From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: [PATCH 1/3] dm: log writes target V2 Date: Tue, 24 Mar 2015 11:33:39 -0400 Message-ID: <20150324153338.GA2055@redhat.com> References: <20150319231655.GA6751@lenny.home.zabbo.net> <1426863037-5870-1-git-send-email-jbacik@fb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, dm-devel@redhat.com, fstests@vger.kernel.org, zab@redhat.com To: Josef Bacik Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44520 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752305AbbCXPdm (ORCPT ); Tue, 24 Mar 2015 11:33:42 -0400 Content-Disposition: inline In-Reply-To: <1426863037-5870-1-git-send-email-jbacik@fb.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Mar 20 2015 at 10:50am -0400, Josef Bacik 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 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