From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: how to repair or access broken btrfs?
Date: Tue, 14 Nov 2017 20:45:26 +0300 [thread overview]
Message-ID: <c43e6c85-2ecc-47a6-2a59-45c65dd693bc@gmail.com> (raw)
In-Reply-To: <32c4071e-4ec0-4d22-95f9-68b22725cff7@profihost.ag>
14.11.2017 12:56, Stefan Priebe - Profihost AG пишет:
> Hello,
>
> after a controller firmware bug / failure i've a broken btrfs.
>
> # parent transid verify failed on 181846016 wanted 143404 found 143399
>
> running repair, fsck or zero-log always results in the same failure message:
> extent-tree.c:2725: alloc_reserved_tree_block: BUG_ON `ret` triggered,
> value -1
> .. stack trace ..
>
> Is there an chance to get at least a single file out of the broken fs?
>
Did you try "btrfs restore"?
next prev parent reply other threads:[~2017-11-14 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:56 how to repair or access broken btrfs? Stefan Priebe - Profihost AG
2017-11-14 17:45 ` Andrei Borzenkov [this message]
2017-11-14 20:31 ` Stefan Priebe - Profihost AG
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=c43e6c85-2ecc-47a6-2a59-45c65dd693bc@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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