linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Michael Zacherl <mz01@bluemole.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Corrupted btrfs (LUKS), seeking advice
Date: Tue, 9 Aug 2022 08:24:27 +0800	[thread overview]
Message-ID: <b817538a-687e-0fee-fa05-a1b0cfe956f3@suse.com> (raw)
In-Reply-To: <60689fac-9a38-9045-262c-7f147d71a3d2@bluemole.com>



On 2022/8/9 01:33, Michael Zacherl wrote:
> On 8/8/22 16:57, Chris Murphy wrote:
>> mount -o ro,rescue=all
>>
>> If that works you can umount and try again adding all the rescue 
>> options except idatacsums.> It's nice to have datacsum warnings 
>> (unless there's just to many errors.)
> 
> rescue=all mounts.
> 
> dmesg from   mount -o 
> ro,rescue=usebackuproot,rescue=nologreplay,rescue=ignorebadroots 
> /dev/mapper/luks-test /mnt :
> 
> [20680.066631] BTRFS info (device dm-1): flagging fs with big metadata 
> feature
> [20680.066641] BTRFS info (device dm-1): trying to use backup root at 
> mount time
> [20680.066646] BTRFS info (device dm-1): disabling log replay at mount time
> [20680.066650] BTRFS info (device dm-1): ignoring bad roots
> [20680.066652] BTRFS info (device dm-1): using free space tree
> [20680.066654] BTRFS info (device dm-1): has skinny extents
> [20680.072359] BTRFS error (device dm-1): parent transid verify failed 
> on 334692352 wanted 14761 found 14765
> [20680.072571] BTRFS error (device dm-1): parent transid verify failed 
> on 334692352 wanted 14761 found 14765
> [20680.073296] BTRFS info (device dm-1): enabling ssd optimizations
> 
> A brief look shows I can access data!
> 
> When also omitting nologreplay the FS wouldn't mount and dmesg shows
> 
> [20837.557120] BTRFS info (device dm-1): flagging fs with big metadata 
> feature
> [20837.557138] BTRFS info (device dm-1): trying to use backup root at 
> mount time
> [20837.557148] BTRFS info (device dm-1): ignoring bad roots
> [20837.557152] BTRFS info (device dm-1): using free space tree
> [20837.557156] BTRFS info (device dm-1): has skinny extents
> [20837.567354] BTRFS error (device dm-1): parent transid verify failed 
> on 334692352 wanted 14761 found 14765
> [20837.567809] BTRFS error (device dm-1): parent transid verify failed 
> on 334692352 wanted 14761 found 14765
> [20837.569387] BTRFS info (device dm-1): enabling ssd optimizationsquite 
> understans
> [20837.569403] BTRFS info (device dm-1): start tree-log replay

Try this mount option "-o ro,rescue=all,rescue=nologreplay".

> [20837.637057] BTRFS error (device dm-1): parent transid verify failed 
> on 337412096 wanted 5492 found 14764
> [20837.637223] BTRFS error (device dm-1): parent transid verify failed 
> on 337412096 wanted 5492 found 14764
> [20837.656541] BTRFS error (device dm-1): parent transid verify failed 
> on 334643200 wanted 14761 found 14765
> [20837.656670] BTRFS error (device dm-1): parent transid verify failed 
> on 334643200 wanted 14761 found 14765
> [20837.656676] BTRFS: error (device dm-1: state A) in 
> btrfs_run_delayed_refs:2151: errno=-5 IO failure
> [20837.656682] BTRFS: error (device dm-1: state EA) in 
> btrfs_replay_log:2567: errno=-5 IO failure (Failed to recover log tree)
> [20837.675238] BTRFS error (device dm-1: state EA): open_ctree failed
> 
> Is this FS repairable to a usable state?

Definitely no.

Thanks,
Qu
> 
> Thanks a lot, Michael.
> 
> 
> 

  reply	other threads:[~2022-08-09  0:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 13:06 Corrupted btrfs (LUKS), seeking advice Michael Zacherl
2022-08-08 16:57 ` Chris Murphy
2022-08-08 17:33   ` Michael Zacherl
2022-08-09  0:24     ` Qu Wenruo [this message]
2022-08-09 11:23       ` Michael Zacherl
2022-08-09 11:37         ` Qu Wenruo
2022-08-10  6:10           ` Andrei Borzenkov
2022-08-10  6:29             ` Qu Wenruo
2022-08-10  7:26               ` Goffredo Baroncelli
2022-08-11  6:40                 ` Qu Wenruo
2022-08-14 13:18                   ` Michael Zacherl
2022-08-09  0:22 ` Qu Wenruo

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=b817538a-687e-0fee-fa05-a1b0cfe956f3@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mz01@bluemole.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).