From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: 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, 09 Mar 2012 09:31:25 +0800 [thread overview]
Message-ID: <4F595D6D.6080809@cn.fujitsu.com> (raw)
In-Reply-To: <CADDYkjTG-q5+pFRFt9sGKq=cgL=ZgQaNZV=2ipBsSbuvxCa3jw@mail.gmail.com>
On 03/09/2012 03:35 AM, Jacek Luczak wrote:
> 2012/3/8 David Sterba <dave@jikos.cz>:
>> On Thu, Mar 08, 2012 at 01:10:45PM +0100, Jacek Luczak wrote:
>>> kernel BUG at fs/btrfs/delayed-inode.c:1466!
>> 1461 ret = btrfs_delayed_item_reserve_metadata(trans, root, item);
>> 1462 /*
>> 1463 * we have reserved enough space when we start a new transaction,
>> 1464 * so reserving metadata failure is impossible.
>> 1465 */
>> 1466 BUG_ON(ret);
>>
>>> RAX: 00000000ffffffe4
>> ENOSPC
>>
>>> [<ffffffffa03210e5>] ? __btrfs_unlink_inode+0x172/0x25e [btrfs]
>>> [<ffffffffa032158c>] ? btrfs_rename+0x38b/0x55b [btrfs]
>> rename reserves 20 blocks, but seems that's not enough. I've never seen
>> a crash report in rename, and according to the stacktrace there's
>> nothing suspicious (like selinux related).
>
> 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
>
Hi Jacek,
So are these warnings based on the latest upstream of btrfs?
thanks,
liubo
> -Jacek
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2012-03-09 1:31 UTC|newest]
Thread overview: 24+ 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-08 19:35 ` Jacek Luczak
2012-03-09 1:31 ` Liu Bo [this message]
2012-03-09 6:43 ` Chris Samuel
2012-03-09 9:15 ` Jacek Luczak
2012-03-09 9:15 ` Jacek Luczak
2012-03-09 10:55 ` David Sterba
2012-03-09 11:08 ` Jacek Luczak
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-11 9:41 ` Jacek Luczak
2012-03-12 14:21 ` Jacek Luczak
2012-03-12 14:21 ` Jacek Luczak
2012-03-12 15:11 ` Johannes Hirte
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=4F595D6D.6080809@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=dave@jikos.cz \
--cc=difrost.kernel@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.