From: Josef Bacik <jbacik@fb.com>
To: Takashi HOSHINO <hoshino@labs.cybozu.co.jp>,
Andreas Dilger <adilger@dilger.ca>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
<linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: crashblk: a block device crash emulator.
Date: Fri, 15 Jan 2016 15:09:52 -0500 [thread overview]
Message-ID: <56995210.2000201@fb.com> (raw)
In-Reply-To: <5698957C.8010508@labs.cybozu.co.jp>
On 01/15/2016 01:45 AM, Takashi HOSHINO wrote:
> Hi Andreas,
>
> On 2016/01/15 4:44, Andreas Dilger wrote:
>> On Jan 13, 2016, at 6:50 PM, Takashi HOSHINO
>> <hoshino@labs.cybozu.co.jp> wrote:
>>>
>>> Hi all,
>>>
>>> I'm developing 'crashblk'.
>>> It is a memory block device driver to emulate crash, IO error,
>>> and various response time.
>>
>> Why not use/improve dm-flakey for this, rather than making yet another
>> device that does something similar?
>
> I did not know dm-flakey until your reply. Thank you.
>
> I read its documents and code a bit.
> The big purpose of two projects are the same, which is to test software
> on block devices with errors, but their functions are almost different.
>
> It may be nice idea to implement alternative implementation of crashblk
> on device-mapper version by someone.
> Currently I'm not familiar with device-mapper development, and I do not
> have any motivation with it.
>
There's also dm-log-writes which will log writes to an external journal
to allow you to replay writes and verify the fs is consistent at all
steps of operation. Thanks,
Josef
next prev parent reply other threads:[~2016-01-15 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 1:50 crashblk: a block device crash emulator Takashi HOSHINO
2016-01-14 19:44 ` Andreas Dilger
2016-01-15 6:45 ` Takashi HOSHINO
2016-01-15 20:09 ` Josef Bacik [this message]
2016-01-18 2:24 ` Takashi HOSHINO
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=56995210.2000201@fb.com \
--to=jbacik@fb.com \
--cc=adilger@dilger.ca \
--cc=hoshino@labs.cybozu.co.jp \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).