From: Josef Bacik <josef@redhat.com>
To: liubo <liubo2009@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix oops while writing data to SSD partitions
Date: Wed, 27 Jul 2011 10:26:12 -0400 [thread overview]
Message-ID: <4E302004.2030007@redhat.com> (raw)
In-Reply-To: <4E2FDF1E.8080206@cn.fujitsu.com>
On 07/27/2011 05:49 AM, liubo wrote:
> Here I have a two SSD-partitions btrfs, and they are defaultly set to
> "data=raid0, metadata=raid1", then I try to fill my btrfs partition
> till "No space left on device", via "dd if=/dev/zero of=/mnt/btrfs/tmp".
>
> I get an oops panic from kernel BUG at fs/btrfs/extent-tree.c:5199!, which
> refers to find_free_extent's
> BUG_ON(index != get_block_group_index(block_group));
>
> In SSD mode, in order to find enough space to alloc, we may check the
> block_group cache which has been checked sometime before, but the index is not
> updated, where it hits the BUG_ON.
>
> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
> ---
> fs/btrfs/extent-tree.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 71cd456..3213c39 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -5065,7 +5065,9 @@ have_block_group:
> * group is does point to and try again
> */
> if (!last_ptr_loop && last_ptr->block_group &&
> - last_ptr->block_group != block_group) {
> + last_ptr->block_group != block_group &&
> + index <=
> + get_block_group_index(last_ptr->block_group)) {
>
> btrfs_put_block_group(block_group);
> block_group = last_ptr->block_group;
Ugh I wish we could make this prettier but
Acked-by: Josef Bacik <josef@redhat.com>
Thanks,
Josef
next prev parent reply other threads:[~2011-07-27 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 9:49 [PATCH] Btrfs: fix oops while writing data to SSD partitions liubo
2011-07-27 14:26 ` Josef Bacik [this message]
2011-07-28 1:11 ` liubo
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=4E302004.2030007@redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@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).