linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: <linux-btrfs@vger.kernel.org>, <dm-devel@redhat.com>,
	<david@fromorbit.com>, <sandeen@redhat.com>, <hch@infradead.org>,
	<linux-fsdevel@vger.kernel.org>, <tytso@mit.edu>,
	<clm@facebook.com>, <zab@redhat.com>
Subject: Re: [PATCH][RFC] dm: log writes target
Date: Thu, 5 Feb 2015 11:56:41 -0500	[thread overview]
Message-ID: <54D3A0C9.3000907@fb.com> (raw)
In-Reply-To: <20150204184108.GA2801@redhat.com>

On 02/04/2015 01:41 PM, Mike Snitzer wrote:
> On Mon, Dec 08 2014 at  5:32P -0500,
> Josef Bacik <jbacik@fb.com> wrote:
>
>> This is my latest attempt at a target for testing power fail and fs consistency.
>> This is based on the idea Zach Brown had where we could just walk through all
>> the operations done to an fs in order to verify we're doing the correct thing.
>> There is a userspace component as well that can be found here
>>
>> https://github.com/josefbacik/log-writes
>>
>> It is very rough as I just threw it together to test the various aspects of how
>> you would want to replay a log to test it.  Again I would love feedback on this,
>> I really want to have something that we all think is usefull and eventually
>> incorporate it into xfstests.
>
> hey josef,
>
> i finally took a quick look at your target.  has this target proven
> useful to you (or others) since you posted?  would you still like to see
> this land upstream?
>
> i see no need to stack discard limits if discards are supported by the
> underlying device (you'll get that for free via blk_stack_limits).
>
> here is a patch that applies ontop of your original submission.  mostly
> whitespace (i'm not pedantic about 80 char limit, etc).  but i did
> include some small improvements and FIXMEs/questions in the patch:
>

Hello,

Yup I still want to land this upstream, I've been using it to find 
balance bugs and other things in btrfs.  With the holidays and all my 
family medical things going on recently I haven't had as much time to 
put into this as I wanted but I've made some improvements to it 
recently.  My plan was to wait until LSF so I could present my ideas to 
all the FS and DM guys at the same time to make sure we were happy with 
this approach and then submit shortly after that.

I will apply this and look through the FIXME's soon and send another 
update to make sure things still look good.  Thanks for looking at this,

Josef

      parent reply	other threads:[~2015-02-05 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 22:32 [PATCH][RFC] dm: log writes target Josef Bacik
2015-02-04 18:41 ` Mike Snitzer
2015-02-04 23:34   ` Mike Snitzer
2015-02-05 16:56   ` Josef Bacik [this message]

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=54D3A0C9.3000907@fb.com \
    --to=jbacik@fb.com \
    --cc=clm@facebook.com \
    --cc=david@fromorbit.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=tytso@mit.edu \
    --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).