From: Daniel J Blueman <daniel.blueman@gmail.com>
To: liubo <liubo2009@cn.fujitsu.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Josef Bacik <josef@redhat.com>,
Linux BTRFS <linux-btrfs@vger.kernel.org>,
Miao Xie <miaox@cn.fujitsu.com>
Subject: Re: [2.6.38-rc6] create->rebalance->mount crash...
Date: Sat, 26 Feb 2011 12:16:15 +0800 [thread overview]
Message-ID: <AANLkTinxLfdYWaab621yOg+M2xKnb=xVgXrmG0NJ7Srd@mail.gmail.com> (raw)
In-Reply-To: <4D665396.2040105@cn.fujitsu.com>
On 24 February 2011 20:48, liubo <liubo2009@cn.fujitsu.com> wrote:
> On 02/24/2011 04:13 PM, Daniel J Blueman wrote:
>> When creating a filesystem (single or redundant) with BTRFS and
>> subsequently executing a balance [1], we see a kernel oops at the ne=
xt
>> mount [2].
>>
>
> Hi, Daniel,
>
> After digging this, I've come up with a patch on this, would you plea=
se test
> it on your box? =A0Hopes that this is helpful, Thanks.
>
> From: Liu Bo <liubo2009@cn.fujitsu.com>
>
> [PATCH] btrfs: fix OOPS of empty filesystem after balance
>
> btrfs will exclude unused block groups via a thread.
> When a empty filesystem is balanced, the block group with tag "DATA" =
may be dropped,
> and after umount, this will lead to OOPS when we mount it again.
[snip]
Thanks, Bo; the patch addresses the oops.
Daniel
Reported-by: Daniel J Blueman <daniel.blueman@gmail.com>
Tested-by: Daniel J Blueman <daniel.blueman@gmail.com>
--=20
Daniel J Blueman
--
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
prev parent reply other threads:[~2011-02-26 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 8:13 [2.6.38-rc6] create->rebalance->mount crash Daniel J Blueman
2011-02-24 12:48 ` liubo
2011-02-24 14:35 ` Chris Mason
2011-02-25 2:19 ` Miao Xie
2011-02-26 4:16 ` Daniel J Blueman [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='AANLkTinxLfdYWaab621yOg+M2xKnb=xVgXrmG0NJ7Srd@mail.gmail.com' \
--to=daniel.blueman@gmail.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=miaox@cn.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).