From: Josef Bacik <jbacik@fusionio.com>
To: Marc MERLIN <marc@merlins.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/volumes.c:3753! These btrfs crashes at mount time on log replay are really a problem
Date: Tue, 26 Feb 2013 09:23:00 -0500 [thread overview]
Message-ID: <20130226142300.GE19641@localhost.localdomain> (raw)
In-Reply-To: <20130226065102.GC11218@merlins.org>
On Mon, Feb 25, 2013 at 11:51:02PM -0700, Marc MERLIN wrote:
> TL;DR;
> WARNING: at fs/btrfs/tree-log.c:1984 walk_down_log_tree+0x51/0x307()
> WARNING: at fs/btrfs/tree-log.c:1988 walk_down_log_tree+0x6c/0x307()
> kernel BUG at fs/btrfs/volumes.c:3753!
>
> It's way time for btrfs to stop crashing your system with no recovery flag
> that works to clear the log if the log can't be replayed. Hell, on non
> development systems, it should just auto discard the log if it can't be
> replayed without user input.
>
>
> Details:
> It's been almost a year that I'm doing my best to test btrfs and report
> bugs, but how quickly it crashes on mount if anything is off, is a huge
> usability problem.
>
> I just again, lost use of my machine today after an unrelated problem caused
> a crash/reboot, and incomplete btrfs writes to my device.
> That happens, it's life.
>
> But after that, I get to roll a dice of whether btrfs will recover, or just
> crash on mount.
> It's slightly more liveable if it's a scratch filesystem on a developer box,
> you just don't mount it.
> It's really really sucky if it's your root filesystem and you need to boot
> from a rescue partition/media to recover each time.
>
> Then, I spent 3 hours reproducing the crash again, with netconsole working
> so that I can get a useful bugreport, which I send here.
So how did you reproduce it? I'll take a fs_image, but being able to reproduce
the problem is more valuable. Thanks,
next prev parent reply other threads:[~2013-02-26 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 6:51 kernel BUG at fs/btrfs/volumes.c:3753! These btrfs crashes at mount time on log replay are really a problem Marc MERLIN
2013-02-26 14:23 ` Josef Bacik [this message]
2013-02-26 16:20 ` Marc MERLIN
2013-02-26 18:24 ` Zach Brown
2013-02-26 19:09 ` Marc MERLIN
2013-02-26 19:28 ` Zach Brown
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=20130226142300.GE19641@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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