From: David Sterba <dave@jikos.cz>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: Jacek Luczak <difrost.kernel@gmail.com>,
dave@jikos.cz, linux-btrfs <linux-btrfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
josef@redhat.com
Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1466!
Date: Fri, 9 Mar 2012 11:55:37 +0100 [thread overview]
Message-ID: <20120309105537.GG4334@twin.jikos.cz> (raw)
In-Reply-To: <4F595D6D.6080809@cn.fujitsu.com>
On Fri, Mar 09, 2012 at 09:31:25AM +0800, Liu Bo wrote:
> > There were quite many things happening in the system at that time.
> > Can't really tell what could trigger this.
> >
> > Complete logs: http://91.234.146.107/~difrost/logs/tampere_log.gz
> >
> So are these warnings based on the latest upstream of btrfs?
No, from the log it's 3.2.7, so it does not conain the patch
"increase the global block reserve estimates"
the log shows lots of messages
Mar 8 13:36:37 kernel: use_block_rsv: 7 callbacks suppressed
Mar 8 13:36:37 kernel: ------------[ cut here ]------------
Mar 8 13:36:37 kernel: WARNING: at fs/btrfs/extent-tree.c:5985 btrfs_alloc_free_block+0xc5/0x292 [btrfs]()
...
Mar 8 13:36:37 kernel: [<ffffffffa031161f>] ? btrfs_alloc_free_block+0xc5/0x292 [btrfs]
Mar 8 13:36:37 kernel: [<ffffffff8106901d>] ? warn_slowpath_common+0x78/0x8d
Mar 8 13:36:37 kernel: [<ffffffffa031161f>] ? btrfs_alloc_free_block+0xc5/0x292 [btrfs]
Mar 8 13:36:37 kernel: [<ffffffffa032bbad>] ? btrfs_item_offset+0x2c/0x61 [btrfs]
Mar 8 13:36:37 kernel: [<ffffffffa03007dc>] ? leaf_space_used+0x86/0xb5 [btrfs]
Mar 8 13:36:39 kernel: [<ffffffffa0304a7a>] ? split_leaf+0x2d9/0x632 [btrfs]
Mar 8 13:36:39 kernel: [<ffffffffa0306261>] ? btrfs_search_slot+0x6c1/0x75a [btrfs]
Mar 8 13:36:40 kernel: [<ffffffffa0306e6e>] ? btrfs_insert_empty_items+0x61/0xab [btrfs]
Mar 8 13:36:41 kernel: [<ffffffffa032207c>] ? insert_inline_extent+0xea/0x2d4 [btrfs]
Mar 8 13:36:41 kernel: [<ffffffffa0322389>] ? cow_file_range_inline+0x123/0x163 [btrfs]
...
so there is probably other problem in reservations and it just blew up during
the unlink call.
david
next prev parent reply other threads:[~2012-03-09 10:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 12:10 kernel BUG at fs/btrfs/delayed-inode.c:1466! Jacek Luczak
2012-03-08 15:52 ` David Sterba
2012-03-08 19:35 ` Jacek Luczak
2012-03-09 1:31 ` Liu Bo
2012-03-09 6:43 ` Chris Samuel
2012-03-09 9:15 ` Jacek Luczak
2012-03-09 10:55 ` David Sterba [this message]
2012-03-09 11:08 ` Jacek Luczak
2012-03-09 11:40 ` David Sterba
2012-03-09 14:13 ` Jacek Luczak
2012-03-09 14:33 ` Jacek Luczak
2012-03-09 14:54 ` David Sterba
2012-03-09 15:32 ` Jacek Luczak
2012-03-09 15:44 ` Jacek Luczak
2012-03-09 23:18 ` Jacek Luczak
2012-03-11 9:41 ` Jacek Luczak
2012-03-12 14:21 ` Jacek Luczak
2012-03-12 15:11 ` Johannes Hirte
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=20120309105537.GG4334@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=difrost.kernel@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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