All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
	<dm-devel@redhat.com>, <zab@redhat.com>,
	<fstests@vger.kernel.org>
Subject: [PATCH 0/3] Device mapper log writes patches
Date: Thu, 19 Mar 2015 16:31:07 -0400	[thread overview]
Message-ID: <1426797070-27463-1-git-send-email-jbacik@fb.com> (raw)

Here are my patches for adding the dm-log-writes target to the kernel and the
supporting xfstests to go along with it.  The dm patch has a pretty detailed
documentation file to describe the methodology behind the target and how to use
it.  The xfstest that is generic has been tested on btrfs, xfs and ext4 and
currently fails on all of them in different ways with my kernel (which is just
3.19 so don't be too alarmed).  The btrfs specific one passes currently, more
evil tests will come later.

Basically the idea behind this target and these tests are to give our file
systems a more thorough power fail scenario testing.  The target logs writes in
order that things would have made it safely to disk and then the tests replay
that log in various ways and check the result.

You can find the supporting userspace program here

https://github.com/josefbacik/log-writes

I apologize for it being ugly, I was trying to get it working as quickly as
possible.  There is an example script in there that you can use to do an
exhaustive step by step through a log to make sure your file system is always
consistent.  Thanks,

Josef


WARNING: multiple messages have this Message-ID (diff)
From: Josef Bacik <jbacik@fb.com>
To: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	dm-devel@redhat.com, zab@redhat.com, fstests@vger.kernel.org
Subject: [PATCH 0/3] Device mapper log writes patches
Date: Thu, 19 Mar 2015 16:31:07 -0400	[thread overview]
Message-ID: <1426797070-27463-1-git-send-email-jbacik@fb.com> (raw)

Here are my patches for adding the dm-log-writes target to the kernel and the
supporting xfstests to go along with it.  The dm patch has a pretty detailed
documentation file to describe the methodology behind the target and how to use
it.  The xfstest that is generic has been tested on btrfs, xfs and ext4 and
currently fails on all of them in different ways with my kernel (which is just
3.19 so don't be too alarmed).  The btrfs specific one passes currently, more
evil tests will come later.

Basically the idea behind this target and these tests are to give our file
systems a more thorough power fail scenario testing.  The target logs writes in
order that things would have made it safely to disk and then the tests replay
that log in various ways and check the result.

You can find the supporting userspace program here

https://github.com/josefbacik/log-writes

I apologize for it being ugly, I was trying to get it working as quickly as
possible.  There is an example script in there that you can use to do an
exhaustive step by step through a log to make sure your file system is always
consistent.  Thanks,

Josef


             reply	other threads:[~2015-03-19 20:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 20:31 Josef Bacik [this message]
2015-03-19 20:31 ` [PATCH 0/3] Device mapper log writes patches Josef Bacik
2015-03-19 20:31 ` [PATCH 1/3] dm: log writes target Josef Bacik
2015-03-19 20:31   ` Josef Bacik
2015-03-19 23:16   ` Zach Brown
2015-03-20 14:50     ` [PATCH 1/3] dm: log writes target V2 Josef Bacik
2015-03-20 14:50       ` Josef Bacik
2015-03-20 16:31       ` Zach Brown
2015-03-24 15:33       ` Mike Snitzer
2015-04-07 14:41         ` Josef Bacik
2015-04-07 14:41           ` Josef Bacik
2015-03-21 21:50   ` [PATCH 1/3] dm: log writes target Dave Chinner
2015-04-07 14:43     ` Josef Bacik
2015-04-07 14:43       ` Josef Bacik
2015-03-23 18:02   ` [dm-devel] " Vivek Goyal
2015-04-07 14:45     ` Josef Bacik
2015-04-07 14:45       ` Josef Bacik
2015-03-19 20:31 ` [PATCH 2/3] fstests: add dm-log-writes test and supporting code Josef Bacik
2015-03-19 20:31   ` Josef Bacik
2015-03-19 20:31 ` [PATCH 3/3] fstests: btrfs balance with dm log writes test Josef Bacik
2015-03-19 20:31   ` Josef Bacik
2015-03-25 10:35   ` Filipe David Manana

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=1426797070-27463-1-git-send-email-jbacik@fb.com \
    --to=jbacik@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zab@redhat.com \
    /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.