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 12:53:21 -0900 [thread overview]
Message-ID: <20161219215306.vmkhgwifrj5ph2qr@moria.home.lan> (raw)
In-Reply-To: <1482181240.24490.9@smtp.office365.com>
On Mon, Dec 19, 2016 at 04:00:40PM -0500, Josef Bacik wrote:
> Ok that works fine in the short term for you, but ideally you wouldn't have
> to fix the test every time you wanted to run it on bcachefs. Do you have a
> suggestion of how to make this generic enough to support you as well without
> dd'ing the whole drive? Thanks,
Yes, but it'd be a lot of work :)
Change log-writes so that instead of replaying the log, you have it create a
block device representing that specific point in the log - and then service read
requests by looking them up however you like. So, it'd be just like mounting
snapshots.
It might not be too difficult since we can deal with crappy performance or
memory usage here, but I don't know if it's really worth the effort.
next prev parent reply other threads:[~2016-12-19 21:53 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 [this message]
2016-12-20 1:01 ` Josef Bacik
2016-12-20 1:30 ` Kent Overstreet
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=20161219215306.vmkhgwifrj5ph2qr@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.