From: Roman Mamedov <rm@romanrm.net>
To: Thomas Wurfbaum <thomas@wurfbaum.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Crashed filesystem, nothing helps
Date: Wed, 2 Aug 2017 14:31:41 +0500 [thread overview]
Message-ID: <20170802143141.71b47fe1@natsu> (raw)
In-Reply-To: <3415313.AO7fCVCIcW@nimrod.thomas.wurfbaum.net>
On Wed, 02 Aug 2017 11:17:04 +0200
Thomas Wurfbaum <thomas@wurfbaum.net> wrote:
> A restore does also not help:
> mainframe:~ # btrfs restore /dev/sdb1 /mnt
> parent transid verify failed on 29392896 wanted 1486833 found 1486836
> parent transid verify failed on 29392896 wanted 1486833 found 1486836
> parent transid verify failed on 29392896 wanted 1486833 found 1486836
> parent transid verify failed on 29392896 wanted 1486833 found 1486836
> Ignoring transid failure
> parent transid verify failed on 29409280 wanted 1486829 found 1486833
> parent transid verify failed on 29409280 wanted 1486829 found 1486833
> parent transid verify failed on 29409280 wanted 1486829 found 1486833
> parent transid verify failed on 29409280 wanted 1486829 found 1486833
> Ignoring transid failure
> parent transid verify failed on 29376512 wanted 1327723 found 1486833
> parent transid verify failed on 29376512 wanted 1327723 found 1486833
> parent transid verify failed on 29376512 wanted 1327723 found 1486833
> parent transid verify failed on 29376512 wanted 1327723 found 1486833
> Ignoring transid failure
Did it just abruptly exit there? Or you terminated it?
IIRC these messages (about ignoring) are not a problem for restore, it should
be able to continue. Or if not, it would print a more definitive error
message, e.g. "Couldn't read tree root" or such.
--
With respect,
Roman
next prev parent reply other threads:[~2017-08-02 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 8:27 Crashed filesystem, nothing helps Thomas Wurfbaum
2017-08-02 8:29 ` Thomas Wurfbaum
2017-08-02 9:07 ` Hugo Mills
2017-08-02 9:17 ` Thomas Wurfbaum
2017-08-02 9:31 ` Roman Mamedov [this message]
2017-08-02 9:33 ` Thomas Wurfbaum
2017-08-02 9:41 ` Thomas Wurfbaum
2017-08-07 5:12 ` Thomas Wurfbaum
2017-08-07 8:47 ` Henk Slager
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=20170802143141.71b47fe1@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=thomas@wurfbaum.net \
/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