From: Nikolay Borisov <nborisov@suse.com>
To: David Radford <croxis@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Unable to mount, even in recovery, parent transid verify failed on raid 1
Date: Wed, 21 Aug 2019 09:20:56 +0300 [thread overview]
Message-ID: <f0574fc5-5343-5b9a-fda9-60ba947d88c9@suse.com> (raw)
In-Reply-To: <CABJoFDA-ZwF3ZDpajHo3288NcV+_NO5BAsXv7yTe_hqqRNv0PQ@mail.gmail.com>
On 20.08.19 г. 21:17 ч., David Radford wrote:
> I have two 2TB spinning disks with full disk btrfs in raid 1. I am
> unable to mount the disks using any method I have found online. I've
> attached what I hope are the relevant logs. I had to edit them down to
> meet the file size limit.
>
> uname: Linux babylon 5.2.9-arch1-1-custom-btrfs #1 SMP PREEMPT Mon Aug
> 19 06:41:35 PDT 2019 x86_64 GNU/Linux (Standard Arch Linux kernel
> compiled with Qu's new rescue patch
> https://patchwork.kernel.org/project/linux-btrfs/list/?series=130637)
SO what event predates this inability to mount? Did you experience any
hard resets - system hangs etc that prompted you to reboot your machine?
Have you changed your kernel recently ? There really isn't much to go on
in here? At the very least DO NOT run any of the repair functionality in
btrfs-progs just yet.
>
> btrfs-progs v5.2.1
>
> [root@babylon ~]# btrfs fi show
> Label: 'linux' uuid: 3fd368de-157c-4512-8985-2be93a21a371
> Total devices 1 FS bytes used 102.48GiB
> devid 1 size 119.24GiB used 110.31GiB path /dev/sdb1
>
> Label: none uuid: 2507581c-dec0-4fdd-afe7-1f7c7ff66c6d (this is the
> one unountable)
> Total devices 2 FS bytes used 1.54TiB
> devid 1 size 1.82TiB used 790.03GiB path /dev/sdc
> devid 2 size 1.82TiB used 790.03GiB path /dev/sdd
>
> mounting with usebackuproot and rescue=skip_bg results in
> [ 1088.130629] BTRFS info (device sdc): trying to use backup root at mount time
> [ 1088.130633] BTRFS info (device sdc): disk space caching is enabled
> [ 1088.130635] BTRFS info (device sdc): has skinny extents
> [ 1088.135907] BTRFS error (device sdc): parent transid verify failed
> on 30425088 wanted 18663 found 18664
> [ 1088.151587] BTRFS error (device sdc): parent transid verify failed
> on 30425088 wanted 18663 found 18664
> [ 1088.151605] BTRFS warning (device sdc): failed to read root (objectid=2): -5
> [ 1088.151902] BTRFS error (device sdc): parent transid verify failed
> on 30425088 wanted 18663 found 18664
> [ 1088.152134] BTRFS error (device sdc): parent transid verify failed
> on 30425088 wanted 18663 found 18664
> [ 1088.152143] BTRFS warning (device sdc): failed to read root (objectid=2): -5
> [ 1088.152519] BTRFS error (device sdc): parent transid verify failed
> on 30425088 wanted 18663 found 18664
> [ 1088.152633] BTRFS error (device sdc): parent transid verify failed
> on 30425088 wanted 18663 found 18664
> [ 1088.152640] BTRFS warning (device sdc): failed to read root (objectid=2): -5
> [ 1088.153462] BTRFS error (device sdc): parent transid verify failed
> on 343428399104 wanted 18163 found 19034
> [ 1088.153690] BTRFS error (device sdc): parent transid verify failed
> on 343428399104 wanted 18163 found 19034
> [ 1088.153699] BTRFS warning (device sdc): failed to read root (objectid=4): -5
> [ 1088.154714] BTRFS error (device sdc): parent transid verify failed
> on 343428399104 wanted 18163 found 19034
> [ 1088.154915] BTRFS error (device sdc): parent transid verify failed
> on 343428399104 wanted 18163 found 19034
> [ 1088.154921] BTRFS warning (device sdc): failed to read root (objectid=4): -5
> [ 1088.261675] BTRFS error (device sdc): open_ctree failed
>
> btrfs-find-root log attached
>
> I do have partial backup but it is a little outdated and would really
> appreciate help either fixing the filesystem, or finding out how to
> recover it with as minimal loss as possible. Thank you for the help!
>
next prev parent reply other threads:[~2019-08-21 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:17 Unable to mount, even in recovery, parent transid verify failed on raid 1 David Radford
2019-08-20 18:56 ` Swâmi Petaramesh
2019-08-21 6:20 ` Nikolay Borisov [this message]
2019-08-21 14:54 ` David Radford
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=f0574fc5-5343-5b9a-fda9-60ba947d88c9@suse.com \
--to=nborisov@suse.com \
--cc=croxis@gmail.com \
--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).