From: Eric Sandeen <sandeen@redhat.com>
To: russell@coker.com.au
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Debian 3.7.1 BTRFS crash
Date: Tue, 12 Mar 2013 21:03:19 -0500 [thread overview]
Message-ID: <513FDE67.1050907@redhat.com> (raw)
In-Reply-To: <201303131238.33692.russell@coker.com.au>
On 3/12/13 8:38 PM, Russell Coker wrote:
> I have a workstation running the Debian packaged 3.7.1 kernel from 24th
> December last year. After some period of uptime (maybe months) it crashed and
> mounted the root filesystem read-only. Now when I boot it the root filesystem
> gets mounted read-only.
>
> I have attached the dmesg output from the last boot.
>
> The system has an Intel 120G SSD and apart from 4G of swap and 400M of /boot
> it's all a single encrypted BTRFS filesystem.
>
> Any suggestions on what I should do next?
Not offhand, but I took a look at the logs, and maybe this will help the
people who are more guru-like than I am.
First you hit:
[ 37.175750] btrfs: corrupt leaf, bad key order: block=70852288512,root=1, slot=8
[ 37.176435] btrfs: corrupt leaf, bad key order: block=70852288512,root=1, slot=8
which led to an aborted transaction and an attempt at graceful shutdown:
[ 37.176478] WARNING: at /build/buildd-linux_3.7.1-1~experimental.1-amd64-lU7Aeh/linux-3.7.1/fs/btrfs/super.c:246 __btrfs_abort_transaction+0x4c/0xcf [btrfs]()
[ 37.176481] btrfs: Transaction aborted
...
[ 37.176790] BTRFS error (device dm-0) in __btrfs_free_extent:5143: IO failure
[ 37.176791] btrfs is forced readonly
[ 37.176793] btrfs: run_one_delayed_ref returned -5
in the end, despite that attempt at graceful exit, you hit:
[ 37.937174] kernel BUG at /build/buildd-linux_3.7.1-1~experimental.1-amd64-lU7Aeh/linux-3.7.1/fs/btrfs/transaction.c:1753!
because in btrfs_clean_old_snapshots(), btrfs_drop_snapshot() failed, and
BUG_ON(ret < 0);
it doesn't handle that well.
I have no idea what btrfsck might do, but it seems like if there is a corrupt
leaf, that might be in order. I might make a device image first, as well.
-Eric
next prev parent reply other threads:[~2013-03-13 2:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 1:38 Debian 3.7.1 BTRFS crash Russell Coker
2013-03-13 1:56 ` Harald Glatt
2013-03-13 2:03 ` Eric Sandeen [this message]
2013-03-13 5:07 ` Jérôme Poulin
2013-03-13 10:56 ` Bart Noordervliet
2013-03-13 11:31 ` Swâmi Petaramesh
2013-03-14 19:04 ` Norbert Scheibner
2013-03-14 23:17 ` Martin Steigerwald
2013-03-13 13:47 ` Eric Sandeen
2013-03-13 14:03 ` Russell Coker
2013-03-13 19:19 ` Chris Mason
2013-03-14 6:36 ` Russell Coker
2013-03-14 13:04 ` Chris Mason
2013-03-14 9:48 ` Martin Steigerwald
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=513FDE67.1050907@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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).