From: Josef Bacik <jbacik@fb.com>
To: Kent Overstreet <kent.overstreet@gmail.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: Sun, 18 Dec 2016 21:19:57 +0000 [thread overview]
Message-ID: <05A4E7E7-E733-4AE9-BDC7-FEE9F66E387D@fb.com> (raw)
In-Reply-To: <20161218204623.gea7u4d3pb7k3zhw@kmo-pixel>
Eeesh these are older than I thought, I pushed to https://github.com/josefbacik/fstests.git. The fsx work is there and is generic, the fsstress one has some btrfs specific stuff but you can just pull that crap out and it'll work on anything. Let me know if you need anything else, thanks,
Josef
Sent from my iPhone
> On Dec 18, 2016, at 3:46 PM, Kent Overstreet <kent.overstreet@gmail.com> wrote:
>
>> On Sun, Dec 18, 2016 at 03:38:54PM -0500, Josef Bacik wrote:
>> On Sun, Dec 18, 2016 at 3:12 PM, Kent Overstreet <kent.overstreet@gmail.com>
>> wrote:
>>> On Thu, Dec 15, 2016 at 04:15:27AM +0000, Josef Bacik wrote:
>>>> dm-log-writes is probably what you want. Thanks,
>>>
>>> Oh, that actually looks pretty cool.
>>>
>>> Don't suppose anyone is working on making use of it in xfstests?
>>
>> Actually I had two xfstests, one that used fsstress and just made sure every
>> commit point was valid (every FUA/FLUSH it found in the log) and then one
>> that modified fsx to output a known good image every time it ran fsync and
>> mark the log to make sure fsync did the correct thing. I need to go back
>> and clean them up and get the upstream, but I've been pretty heavily
>> distracted with other things for the last year or two. I'll make getting
>> those upstream a priority after Christmas. Thanks,
>
> Don't suppose you could throw up just what you've currently got somewhere? It'd
> save me some work.
next prev parent reply other threads:[~2016-12-18 21:20 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 [this message]
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
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=05A4E7E7-E733-4AE9-BDC7-FEE9F66E387D@fb.com \
--to=jbacik@fb.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=kent.overstreet@gmail.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.