linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: liubo <liubo2009@cn.fujitsu.com>
Cc: Tsutomu Itoh <t-itoh@jp.fujitsu.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:6164!
Date: Tue, 07 Jun 2011 11:46:37 -0400	[thread overview]
Message-ID: <1307461229-sup-9822@shiny> (raw)
In-Reply-To: <4DEDE328.5060405@cn.fujitsu.com>

Excerpts from liubo's message of 2011-06-07 04:36:56 -0400:
> On 06/07/2011 04:24 PM, Tsutomu Itoh wrote:
> > (2011/06/07 15:17), Tsutomu Itoh wrote:
> >> (2011/06/07 14:59), Tsutomu Itoh wrote:
> >>> Hi liubo,
> >>>
> >>> (2011/06/07 14:31), liubo wrote:
> >>>> On 06/06/2011 04:33 PM, Tsutomu Itoh wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I encountered following panic using 'btrfs-unstable + for-linus'
> >>>>> kernel.
> >>>>>
> >>>>> I ran "btrfs fi bal /test5" command, and mount option of /test5
> >>>>> is as follows:
> >>>>>
> >>>>>  /dev/sdc3 on /test5 type btrfs (rw,space_cache,compress=lzo,inode_cache)
> >>>>>
> >>>> So, just a "btrfs fi bal" would lead to the bug?
> >>> I think so.

It should be specific to the inode caching code.  The balancing code is
finding the inode map cache extents, but it doesn't know how to relocate
them.

I think we need to switch the inode map cache over to regular extents
that are not preallocated.  It will fix the overflow problem and it will
fix the balancing.

There are a lot of special cases for the free extent cache that don't
apply to the inode map cache, and I think sharing the extent
preallocation is hurting us.

-chris

  reply	other threads:[~2011-06-07 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  8:33 kernel BUG at fs/btrfs/extent-tree.c:6164! Tsutomu Itoh
2011-06-07  5:31 ` liubo
2011-06-07  5:59   ` Tsutomu Itoh
2011-06-07  6:17     ` Tsutomu Itoh
2011-06-07  8:24       ` Tsutomu Itoh
2011-06-07  8:36         ` liubo
2011-06-07 15:46           ` Chris Mason [this message]
2011-06-08  5:12             ` Tsutomu Itoh
2011-06-13  7:13               ` bug caused by removal of trans_mutex? (Was: Re: kernel BUG at fs/btrfs/extent-tree.c:6164!) Li Zefan
2011-06-13  7:49                 ` Yan, Zheng 
2011-06-13  8:26                   ` Li Zefan
2011-06-13 13:12                 ` Chris Mason
2011-06-13 15:18                   ` Chris Mason
2011-06-13 14:58                 ` Yan, Zheng 
2011-06-13 15:09                   ` Chris Mason
2011-06-13 19:55                   ` Chris Mason
2011-06-14  3:24                     ` Yan, Zheng 
2011-06-14  5:44                       ` Li Zefan
2011-06-14  6:53                 ` Yan, Zheng 

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=1307461229-sup-9822@shiny \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=liubo2009@cn.fujitsu.com \
    --cc=t-itoh@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).