From: Mike Snitzer <snitzer@redhat.com>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dm-devel@redhat.com, fstests@vger.kernel.org, zab@redhat.com
Subject: Re: [PATCH 1/3] dm: log writes target V2
Date: Tue, 24 Mar 2015 11:33:39 -0400 [thread overview]
Message-ID: <20150324153338.GA2055@redhat.com> (raw)
In-Reply-To: <1426863037-5870-1-git-send-email-jbacik@fb.com>
On Fri, Mar 20 2015 at 10:50am -0400,
Josef Bacik <jbacik@fb.com> wrote:
> This creates a new target that is meant for file system developers to test file
> system integrity at particular points in the life of a file system. We capture
> all write requests and the data and log the requests and the data to a separate
> device for later replay. There is a userspace utility to do this replay. The
> idea behind this is to give file system developers to verify that the file
> system is always consistent. Thanks,
>
> Signed-off-by: Josef Bacik <jbacik@fb.com>
Hey Josef,
Nice job with this target, you need to contribute to DM more ;)
I've staged your target for the 4.1 merge in linux-dm.git's 'for-next'
branch (with a few small fixes for nits/typos).
FYI, I'll likely rebase 'for-next' once more for 4.1 given a conflicting
4.0 change to DM core still needs to land upstream (you can see the
merge conflict in 'for-next' at the moment). But that won't impact your
target at all (other than changing the 4.1 commit id).
Thanks,
Mike
next prev parent reply other threads:[~2015-03-24 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 23:16 ` Zach Brown
2015-03-20 14:50 ` [PATCH 1/3] dm: log writes target V2 Josef Bacik
2015-03-20 16:31 ` Zach Brown
2015-03-24 15:33 ` Mike Snitzer [this message]
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-03-23 18:02 ` [dm-devel] " Vivek Goyal
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 ` [PATCH 3/3] fstests: btrfs balance with dm log writes test 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=20150324153338.GA2055@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jbacik@fb.com \
--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 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).