From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unmountable / uncheckable Fedora 34 btrfs: failed to read block groups: -5 open_ctree failed
Date: Sun, 12 Sep 2021 06:46:24 -0400 [thread overview]
Message-ID: <5b83677221e203dca518234bfd3c47ad@linuxsystems.it> (raw)
In-Reply-To: <a38098d2c2cf96c367707635791b06f9@linuxsystems.it>
Il 2021-09-12 06:44 Niccolò Belli ha scritto:
> Il 2021-09-12 06:27 Niccolò Belli ha scritto:
>> I did manage to recover some data with btrfs restore (no idea how much
>> of it):
>>
>> $ sudo btrfs restore /dev/nvme0n1p6
>> /run/media/liveuser/3ea0705c-21c9-4ba9-80ee-5a511cb2a093/nvme0n1p6_restore/
>> Skipping snapshot snapshot
>> [...lots of snapper snapshots]
>> Skipping snapshot root
>
> I just noticed it completely skipped to restore my root subvolume.
> Maybe because it was originally restored from a snapshot (during a
> previous btrfs corruption issue) and so somehow it thinks it's still a
> snapshot?
> How can I restore it? I cannot afford to restore all the snapshots, I
> don't have enough free space to do so.
Even better would be to restore a snapper snapshot of my root subvolume
(that way it would be less likely to be corrupted).
next prev parent reply other threads:[~2021-09-12 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 10:27 Unmountable / uncheckable Fedora 34 btrfs: failed to read block groups: -5 open_ctree failed Niccolò Belli
2021-09-12 10:44 ` Niccolò Belli
2021-09-12 10:46 ` Niccolò Belli [this message]
2021-09-12 11:14 ` Qu Wenruo
2021-09-12 11:41 ` Niccolò Belli
2021-09-12 13:35 ` Qu Wenruo
2021-09-12 15:51 ` Niccolò Belli
2021-09-13 14:50 ` Zygo Blaxell
2021-09-13 20:40 ` Niccolò Belli
2021-09-12 21:23 ` Niccolò Belli
2021-09-12 23:55 ` Qu Wenruo
2021-09-13 7:16 ` Niccolò Belli
2021-09-13 8:05 ` Qu Wenruo
2021-09-13 11:58 ` Niccolò Belli
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=5b83677221e203dca518234bfd3c47ad@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--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