From: Karl-Philipp Richter <richter@richtercloud.de>
To: linux-btrfs@vger.kernel.org
Subject: Endless (logging of) transid failure in btrfsck after chunk-recover with btrfs-progs 3.18 on Linux 3.17.7
Date: Mon, 05 Jan 2015 12:34:41 +0100 [thread overview]
Message-ID: <54AA76D1.4080602@richtercloud.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Hi,
After running `sudo btrfs rescue chunk-recover -y -v /dev/loop0` with 4
unrecoverable chunks (of 619) I'm having trouble with `btrfsck` which logs
parent transid verify failed on 4210688 wanted 61241 found 7983179
Ignoring transid failure
apparently for ever (let it run for 1 hour which produced the entry >
3.5M times, then killed it). There must be something wrong because the
program needs to succeed or fail, right? After aborting `btrfsck`
`btrfs-debug-tree` and `btrfs-zero-log` both fail with
Check tree block failed, want=16384, have=0
read block failed check_tree_block
Couldn't read chunk root
unable to open /dev/loop0
Please find attached the output of `rescue chunk-recover` and `btrfsck`.
The filesystem is on a `dd` image, mounted via a loop device with
`losetup`. This is the only version of the filesystem I have. I'm
running Ubuntu 14.10 amd64. I can't test 3.18.1 and 3.19rc2.
Any help or hints are appreciated.
Best regards,
Kalle
[-- Attachment #2: chuck-recover_btrfsck_failure.log.tar.xz --]
[-- Type: application/x-xz, Size: 14956 bytes --]
reply other threads:[~2015-01-05 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54AA76D1.4080602@richtercloud.de \
--to=richter@richtercloud.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).