From: Liu Bo <liubo2009@cn.fujitsu.com>
To: David Sterba <dave@jikos.cz>
Cc: linux-btrfs@vger.kernel.org, chris.mason@oracle.com, sensille@gmx.net
Subject: Re: [PATCH 0/5] fix bugs of sub transid
Date: Tue, 29 Nov 2011 09:18:35 +0800 [thread overview]
Message-ID: <4ED432EB.2070706@cn.fujitsu.com> (raw)
In-Reply-To: <20111128151030.GK12759@twin.jikos.cz>
On 11/28/2011 11:10 PM, David Sterba wrote:
> On Mon, Nov 21, 2011 at 06:10:19PM +0800, Liu Bo wrote:
>> We've been sufferring two big bugs with sub transid:
>> one is a bug related to root's last_snapshot, the other is a bug related to
>> disk extent refs' generation.
>
> Do you have a testcase to trigger and check these bugs?
>
Hi, David,
a) For the first one (last_snapshot bug),
The test involves three processes (derived from Chris):
mkfs.btrfs /dev/xxx
mount /dev/xxx /mnt
1) run compilebench -i 30 --makej -D /mnt
Let compilebench run until it starts the create phase.
2) run synctest -f -u -n 200 -t 3 /mnt
3) for x in `seq 1 200` ; do btrfs subvol snap /mnt /mnt/snap$x ; sleep 0.5 ; done
b) For the second one,
1) build a btrfs partition, and
2) fill something, and then
3) run balance on it.
>> 1) The first patch fixes a warning,
>> 2) the second one fixes the last_snapshot bug,
>> 3) the third one has already been in for-linus branch, but not in "danger"
>> branch, so I add it here for the integrity,
>> 4) the fourth one fixes a transid mismatch bug,
>> 5) the fifth one fixes the disk extent refs' generation bug.
>>
>> Any advices and tests are welcome!
>
> I have rebased this series on top of current cmason/for-linus (24a70313969),
> should anybody want to test.
>
> (repo address: http://repo.or.cz/w/linux-2.6/btrfs-unstable.git )
>
Great! Thanks for what you've done!
thanks,
liubo
>
> david
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-11-29 1:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 10:10 [PATCH 0/5] fix bugs of sub transid Liu Bo
2011-11-21 10:10 ` [PATCH 1/5] Btrfs: fix btrfs_copy_root warning Liu Bo
2011-11-21 10:10 ` [PATCH 2/5] Btrfs: fix bug with heavy snapshot and heavy fsync Liu Bo
2011-11-21 10:10 ` [PATCH 3/5] Btrfs: fix inconsistent tree Liu Bo
2011-11-21 10:10 ` [PATCH 4/5] Btrfs: filter shared blocks in should_cow_block Liu Bo
2011-11-21 10:10 ` [PATCH 5/5] Btrfs: update disk extent ref generation Liu Bo
2011-11-28 15:10 ` [PATCH 0/5] fix bugs of sub transid David Sterba
2011-11-29 1:18 ` Liu Bo [this message]
2011-11-29 16:17 ` [PATCH 0/5] fix bugs of sub transid -- WARNING: at fs/btrfs/ctree.c:432 David Sterba
2011-12-01 1:32 ` Liu Bo
2011-12-02 16:30 ` David Sterba
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=4ED432EB.2070706@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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).