All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Josef Bacik <jbacik@fb.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"david@fromorbit.com" <david@fromorbit.com>,
	"hch@lst.de" <hch@lst.de>
Subject: Re: Simulating disk failure with a writeback cache
Date: Mon, 19 Dec 2016 16:30:41 -0900	[thread overview]
Message-ID: <20161220013041.rv3ijgyp46w3scba@moria.home.lan> (raw)
In-Reply-To: <3A97B8BF-B65F-4A7D-878F-82D73327B3A9@fb.com>

On Tue, Dec 20, 2016 at 01:01:29AM +0000, Josef Bacik wrote:
> One thing I was definitely going to do is use the dm thin provisioning so I
> could snapshot between each check so we don't have to replay from the
> beginning every time we want to check a different mark.  Replaying the whole
> thing is fine for small runs like the fsx thing, but when you want to say run
> fsstress for a minute and replay to every fua and fsck and mount it gets
> tedious fast.  Thanks,

I actually just converted my new test to do that:

https://evilpiepirate.org/git/ktest.git/commit/

now, most of the time in the test is spent in mount/unmount (bcachefs doesn't
have a standalone fsck yet, we check everything fsck should but it's done at
mount time).

      reply	other threads:[~2016-12-20  1:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  2:26 Simulating disk failure with a writeback cache Kent Overstreet
2016-12-15  4:15 ` Josef Bacik
2016-12-18 20:12   ` Kent Overstreet
2016-12-18 20:38     ` Josef Bacik
2016-12-18 20:46       ` Kent Overstreet
2016-12-18 21:19         ` Josef Bacik
2016-12-19  2:51           ` Kent Overstreet
2016-12-19  3:07             ` Kent Overstreet
2016-12-19 12:58               ` Josef Bacik
2016-12-19 15:27               ` Josef Bacik
2016-12-19 20:55                 ` Kent Overstreet
2016-12-19 21:00                   ` Josef Bacik
2016-12-19 21:53                     ` Kent Overstreet
2016-12-20  1:01                       ` Josef Bacik
2016-12-20  1:30                         ` Kent Overstreet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161220013041.rv3ijgyp46w3scba@moria.home.lan \
    --to=kent.overstreet@gmail.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=jbacik@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.