From: "Martin Fahr" <maf@gmx.eu>
To: linux-btrfs@vger.kernel.org
Subject: another messed-up btrfs
Date: Fri, 01 Apr 2011 21:47:13 +0200 [thread overview]
Message-ID: <20110401194713.6990@gmx.net> (raw)
Hi,
I have put a linux system on an external SSD recently, using btrfs for both root (/) and /home. After a couple of hibernation cycles the system got stuck and I had to reboot it ignoring the memory image on disk. Unfortunately, even a normal reboot did not work anymore. The kernel complains about not being able to mount the root filesystem.
I connected the disk to another system, where the two partitions were not mountable either. btrfsck gave:
> btrfsck /dev/sdc2 #this was root
btrfsck: disk-io.c:741: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
Aborted
Taking advice from some earlier emails I have found on this list, I downloaded the recent btrfsck code using git, compiled it, and did:
> btrfsck -s 1 /dev/sdc2
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
using SB copy 1, bytenr 67108864
Aborted
> btrfsck -s 2 /dev/sdc2
No valid Btrfs found on /dev/sdc2
using SB copy 2, bytenr 274877906944
The same commands for the other partition on the disk gives different messages, but still an unusable file system:
> btrfsck /dev/sdc4
parent transid verify failed on 59128545280 wanted 7937 found 7934
parent transid verify failed on 59128545280 wanted 7937 found 7934
parent transid verify failed on 59128545280 wanted 7937 found 7934
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
> btrfsck -s 1 /dev/sdc4
parent transid verify failed on 59128545280 wanted 7937 found 7934
parent transid verify failed on 59128545280 wanted 7937 found 7934
parent transid verify failed on 59128545280 wanted 7937 found 7934
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
using SB copy 1, bytenr 67108864
> btrfsck -s 2 /dev/sdc4
No valid Btrfs found on /dev/sdc4
using SB copy 2, bytenr 274877906944
The usual questions: Is there anything I could do to help analyze and fix the problem? Is there hope to restore the data any time soon, or should I better use the backup I have (and possibly move to an ext4 file system)?
Thx
Martin
next reply other threads:[~2011-04-01 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 19:47 Martin Fahr [this message]
2011-04-01 20:01 ` another messed-up btrfs Peter Stuge
2011-04-02 0:05 ` Viacheslav Dobromyslov
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=20110401194713.6990@gmx.net \
--to=maf@gmx.eu \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.