From: Malte Eggers <m.eggers@campus.tu-berlin.de>
To: <linux-btrfs@vger.kernel.org>
Subject: BTRFS not mountable, recover won't work
Date: Sun, 9 Apr 2017 19:17:40 +0200 [thread overview]
Message-ID: <1491758260.15056.2.camel@campus.tu-berlin.de> (raw)
Hi,
After suspending and waking up my laptop with the external hard drive
connected, I could no longer access the files on it. So I unmounted and
remounted it, only to discover that I could no longer mount it.
This is the error (mounting with usebackuproot, same error without):
[891667.002861] BTRFS info (device dm-0): trying to use backup root at
mount time
[891667.002870] BTRFS info (device dm-0): disk space caching is enabled
[891667.002876] BTRFS info (device dm-0): has skinny extents
[891667.016395] BTRFS error (device dm-0): parent transid verify failed
on 108855296 wanted 32139 found 32104
[891667.017181] BTRFS error (device dm-0): parent transid verify failed
on 108855296 wanted 32139 found 32104
[891667.017194] BTRFS error (device dm-0): failed to recover balance:
-5
[891667.078829] BTRFS error (device dm-0): open_ctree failed
btrfs restore and btrfs-find-root fail like this (on both debian sid
and fedora 25):
parent transid verify failed on 108806144 wanted 32139 found 32104
parent transid verify failed on 108806144 wanted 32139 found 32104
parent transid verify failed on 108806144 wanted 32139 found 32104
parent transid verify failed on 108806144 wanted 32139 found 32104
Ignoring transid failure
volumes.c:1645: btrfs_chunk_readonly: BUG_ON `!ce` triggered, value 1
btrfs(+0x530d5)[0x5634cfb180d5]
btrfs(btrfs_chunk_readonly+0x5a)[0x5634cfb1a3b3]
btrfs(btrfs_read_block_groups+0x1dc)[0x5634cfb0fb0c]
btrfs(btrfs_setup_all_roots+0x336)[0x5634cfb0b158]
btrfs(+0x4654c)[0x5634cfb0b54c]
btrfs(open_ctree_fs_info+0xd7)[0x5634cfb0b673]
btrfs(cmd_restore+0x339)[0x5634cfaf93dc]
btrfs(main+0x12f)[0x5634cfadca6b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f3f7161f2b1]
btrfs(_start+0x2a)[0x5634cfadcaaa]
Aborted
How would I go about recovering my Data?
Thanks,
Malte
next reply other threads:[~2017-04-09 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 17:17 Malte Eggers [this message]
2017-04-09 21:25 ` BTRFS not mountable, recover won't work Chris Murphy
2017-04-10 2:38 ` Duncan
2017-04-10 7:55 ` Malte Eggers
2017-04-10 8:18 ` Qu Wenruo
2017-04-10 8:37 ` Malte Eggers
2017-04-10 8:53 ` Qu Wenruo
2017-04-10 10:40 ` Malte Eggers
2017-04-13 11:45 ` Malte Eggers
2017-04-14 0:40 ` Qu Wenruo
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=1491758260.15056.2.camel@campus.tu-berlin.de \
--to=m.eggers@campus.tu-berlin.de \
--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 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).