From: Roman Mamedov <rm@romanrm.net>
To: Lionel Bouton <lionel-subscription@bouton.name>
Cc: Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: help : "bad tree block start" -> btrfs forced readonly
Date: Fri, 17 Mar 2017 14:51:07 +0500 [thread overview]
Message-ID: <20170317145107.21bb9b45@natsu> (raw)
In-Reply-To: <2994d13d-c65c-0794-8a83-a68ff258f109@bouton.name>
On Fri, 17 Mar 2017 10:27:11 +0100
Lionel Bouton <lionel-subscription@bouton.name> wrote:
> Hi,
>
> Le 17/03/2017 à 09:43, Hans van Kranenburg a écrit :
> > btrfs-debug-tree -b 3415463870464
>
> Here is what it gives me back :
>
> btrfs-debug-tree -b 3415463870464 /dev/sdb
> btrfs-progs v4.6.1
> checksum verify failed on 3415463870464 found A85405B7 wanted 01010101
> checksum verify failed on 3415463870464 found A85405B7 wanted 01010101
> bytenr mismatch, want=3415463870464, have=72340172838076673
> ERROR: failed to read 3415463870464
>
> Is there a way to remove part of the tree and keep the rest ? It could
> help minimize the time needed to restore data.
If you are able to experiment with writable snapshots, you could try using
"btrfs-corrupt-block" to kill the bad block, and see what btrfsck makes out of
the rest. In a similar case I got little to no damage to the overall FS.
http://www.spinics.net/lists/linux-btrfs/msg53061.html
--
With respect,
Roman
next prev parent reply other threads:[~2017-03-17 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 4:32 help : "bad tree block start" -> btrfs forced readonly Lionel Bouton
2017-03-17 8:11 ` Lionel Bouton
2017-03-17 8:43 ` Hans van Kranenburg
2017-03-17 9:27 ` Lionel Bouton
2017-03-17 9:42 ` Hans van Kranenburg
2017-03-17 9:51 ` Roman Mamedov [this message]
2017-03-17 10:03 ` Lionel Bouton
2017-03-17 14:17 ` Lionel Bouton
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=20170317145107.21bb9b45@natsu \
--to=rm@romanrm.net \
--cc=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lionel-subscription@bouton.name \
/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