From: Heinz Werner Kramski-Grote <kramski@web.de>
To: linux-btrfs@vger.kernel.org, quwenruo@cn.fujitsu.com
Subject: Re: Unable to repair "bad key order": Cyclic bad block flip-flop
Date: Wed, 14 Sep 2016 12:48:49 +0200 [thread overview]
Message-ID: <2645291.NjGXSRg41N@haspl> (raw)
In-Reply-To: <6c6c8a43-e443-f6ce-4778-24398d118c9b@cn.fujitsu.com>
On Dienstag, 13. September 2016 08:39:27 CEST Qu Wenruo wrote:
> You could try using backup roots to avoid corrupted tree root.
> And it may also fix your extent tree.
> ---
> # btrfs-show-super -f
> ...
> backup_roots[4]:
> backup 0:
> backup_tree_root: 31932416 gen: 10 level: 0
> backup_chunk_root: 20971520 gen: 7 level: 0
[...]
>
> That "backup_tree_root" is what you're looking for.
>
> And use btrfsck with "-r <backup_tree_root_bytenr>" to check if the bad
> order problem disappear.
Thanks, Qu, but this did not help (tried all four positions).
Will do a clean setup.
Regards,
Heinz
prev parent reply other threads:[~2016-09-14 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 21:27 Unable to repair "bad key order": Cyclic bad block flip-flop Heinz Werner Kramski-Grote
2016-09-12 21:32 ` Heinz Werner Kramski-Grote
2016-09-13 0:39 ` Qu Wenruo
2016-09-14 10:48 ` Heinz Werner Kramski-Grote [this message]
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=2645291.NjGXSRg41N@haspl \
--to=kramski@web.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/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).