From: David Sterba <dave@jikos.cz>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: dave@jikos.cz, Liu Bo <liubo2009@cn.fujitsu.com>,
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 12:40:10 +0100 [thread overview]
Message-ID: <20120309114010.GH4334@twin.jikos.cz> (raw)
In-Reply-To: <CADDYkjRcRbxxPErdMBOs55-gNHZA0GfxcsWNrVbAuv37b3rtvw@mail.gmail.com>
On Fri, Mar 09, 2012 at 12:08:12PM +0100, Jacek Luczak wrote:
> For this one I've created also a report [1].
> >
> > so there is probably other problem in reservations and it just blew up during
> > the unlink call.
>
> Could be as this came up after a longer time of throwing above WARN_ON.
>
> I'm now cloning the Linus tree. Lets see if both will pop up on there.
The 3.3-rc6 should help in one case, with
http://thread.gmane.org/gmane.comp.file-systems.btrfs/15268
but I was able to reproduce the WARN_ON even with this patch, didn't get
to debugging it again yet.
david
next prev parent reply other threads:[~2012-03-09 11:40 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
2012-03-09 11:08 ` Jacek Luczak
2012-03-09 11:40 ` David Sterba [this message]
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=20120309114010.GH4334@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