From: David Woodhouse <dwmw2@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Josef Bacik <josef@redhat.com>,
Marek Otahal <markotahal@gmail.com>,
Daniel J Blueman <daniel.blueman@gmail.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Andy Lutomirski <luto@mit.edu>
Subject: Re: kernel BUG at fs/btrfs/inode.c:4676!
Date: Wed, 20 Jul 2011 07:37:50 -0700 [thread overview]
Message-ID: <1311172680.7531.18.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1311150979-sup-1740@shiny>
On Wed, 2011-07-20 at 04:44 -0400, Chris Mason wrote:
> Oh, the dirty little secret of loop devices is they don't actually write
> things to disk properly. They are not power off safe. But you can
> trigger this without a loop device, correct?
Yes. I would have liked to reproduce it last night and show it to you
this morning, and that way I'd double-check that it really is the *same*
BUG(). But certainly I thought it was a few weeks ago when I looked, and
the bit about having to reboot into 2.6.38 before I can boot 3.0 is
*definitely* the same.
> The oops were hitting is a -EEXIST on trying to insert the directory
> entry for the inode back ref, but the tree-logging stuff is already
> trying to check for dups.
>
> I'll take a look.
Thanks. I'll *try* to make it happen again, but I haven't managed it so
far... and no, I haven't updated my kernel; this is the *same* kernel
that was doing it before.
next prev parent reply other threads:[~2011-07-20 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 10:19 kernel BUG at fs/btrfs/inode.c:4676! Marek Otahal
2011-06-08 18:43 ` Marek Otahal
2011-06-09 15:39 ` Jan Steffens
2011-06-10 1:57 ` Andy Lutomirski
2011-06-10 2:06 ` Daniel J Blueman
2011-06-10 13:33 ` Josef Bacik
[not found] ` <201106102043.19025.markotahal@gmail.com>
2011-06-10 18:55 ` Andrew Lutomirski
2011-06-10 20:52 ` Josef Bacik
2011-06-10 21:52 ` Marek Otahal
2011-06-22 16:09 ` Josef Bacik
2011-07-20 6:05 ` David Woodhouse
2011-07-20 8:44 ` Chris Mason
2011-07-20 14:37 ` David Woodhouse [this message]
2011-09-17 19:13 ` Stephane Chazelas
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=1311172680.7531.18.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=chris.mason@oracle.com \
--cc=daniel.blueman@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=luto@mit.edu \
--cc=markotahal@gmail.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).