linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonlist@gmail.com>
To: Josef Bacik <jbacik@fb.com>, lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] Working towards better power fail testing
Date: Tue, 13 Jan 2015 20:05:06 +0300	[thread overview]
Message-ID: <87r3uy3931.fsf@openvz.org> (raw)
In-Reply-To: <5486221D.6000006@fb.com>

Josef Bacik <jbacik@fb.com> writes:

> Hello,
>
> We have been doing pretty well at populating xfstests with loads of 
> tests to catch regressions and validate we're all working properly.  One 
> thing that has been lacking is a good way to verify file system 
> integrity after a power fail.  This is a core part of what file systems 
> are supposed to provide but it is probably the least tested aspect.  We 
> have dm-flakey tests in xfstests to test fsync correctness, but these 
> tests do not catch the random horrible things that can go wrong.  We are 
> still finding horrible scary things that go wrong in Btrfs because it is 
> simply hard to reproduce and test for.
>
> I have been working on an idea to do this better, some may have seen my 
> dm-power-fail attempt, and I've got a new incarnation of the idea thanks 
> to discussions with Zach Brown.  Obviously there will be a lot changing 
> in this area in the time between now and March but it would be good to 
> have everybody in the room talking about what they would need to build a 
> good and deterministic test to make sure we're always giving a 
> consistent file system and to make sure our fsync() handling is working 
> properly.  Thanks,
I've submitted generic/019 long time ago. Test is fine and helps to
uncover several bugs, But it is not ideal because currently power failure
simulation (via fail_make_request) is not not completely atomic
So I would like to attend to discussion how we can implement power
failure simulation completely atomic.

BTW I also would like to share hw-flush utility (which our QA team use for
use power-fail/SSD-cache testing) and harness for it.

  parent reply	other threads:[~2015-01-13 17:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 22:11 [LSF/MM TOPIC] Working towards better power fail testing Josef Bacik
2014-12-10 11:27 ` [Lsf-pc] " Jan Kara
2014-12-10 15:09   ` Josef Bacik
2015-01-05 18:34     ` Sage Weil
2015-01-05 19:02       ` Brian Foster
2015-01-05 19:13         ` Sage Weil
2015-01-05 19:33           ` Brian Foster
2015-01-05 21:17       ` Jan Kara
2015-01-05 21:47       ` Dave Chinner
2015-01-05 22:26         ` Sage Weil
2015-01-05 23:27           ` Dave Chinner
2015-01-06 17:37             ` Sage Weil
2015-01-06  8:53         ` Jan Kara
2015-01-06 16:39           ` Josef Bacik
2015-01-06 22:07           ` Dave Chinner
2015-01-07 10:10             ` Jan Kara
2015-01-13 17:05 ` Dmitry Monakhov [this message]
2015-01-13 17:17   ` Josef Bacik

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=87r3uy3931.fsf@openvz.org \
    --to=dmonlist@gmail.com \
    --cc=jbacik@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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).