From: David Sterba <dave@jikos.cz>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: 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: Thu, 8 Mar 2012 16:52:11 +0100 [thread overview]
Message-ID: <20120308155211.GF4334@twin.jikos.cz> (raw)
In-Reply-To: <CADDYkjQHvmfhmsdt7K0O74DZK6BVqxPaWh_jEi8uJ_HBEz-QhQ@mail.gmail.com>
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).
david
next prev parent reply other threads:[~2012-03-08 15:52 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 [this message]
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
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=20120308155211.GF4334@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 \
/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