linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: dsterba@suse.cz
Cc: Josef Bacik <jbacik@fusionio.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Seto Hidetoshi <seto.hidetoshi@jp.fujitsu.com>,
	David Sterba <dave@jikos.cz>
Subject: Re: [PATCH V3 2/2] Btrfs: fix the snapshot that should not exist
Date: Thu, 09 Aug 2012 11:28:57 +0800	[thread overview]
Message-ID: <50232E79.1060408@cn.fujitsu.com> (raw)
In-Reply-To: <20120808133841.GC5873@ds.suse.cz>

On Wed, 8 Aug 2012 15:38:41 +0200, David Sterba wrote:
> On Sat, Aug 04, 2012 at 01:53:28PM +0800, Miao Xie wrote:
>> But I'm not sure these two bugs is the same, so I need the test tool
>> of David to look into it.
> 
> Attached. It's a set of scripts and has a few assumptions hardcoded,
> like where the tar srouce is and the name of extracted directory, so
> it'll need a few tweaks. Also the actions are started inside a tmux
> session for convenience.
> 
> The expected stress load is to generate lots of files and directories,
> snapshot create and delete and rm of the untarred directory. The 'rm'
> step is delayed a few minutes so the tar generates enough data. On some
> hosts the rm phase is fast and will clean the untar directory too
> quickly.

Thanks.

I find this bug you reported is not introduced by my patch, it is a old bug.
I have sent a RFC patch, I'll be very appreciated if you can get any comment.

Regards
Miao

  reply	other threads:[~2012-08-09  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02  4:40 [PATCH V3 2/2] Btrfs: fix the snapshot that should not exist Miao Xie
2012-08-02 11:46 ` David Sterba
2012-08-03  1:53   ` Miao Xie
2012-08-03 21:03     ` Josef Bacik
2012-08-04  5:53       ` Miao Xie
2012-08-08 13:38         ` David Sterba
2012-08-09  3:28           ` Miao Xie [this message]
2012-09-18 19:24   ` Mitch Harder

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=50232E79.1060408@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=dave@jikos.cz \
    --cc=dsterba@suse.cz \
    --cc=fengguang.wu@intel.com \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.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).