All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: Qu Wenruo <wqu@suse.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Unmountable / uncheckable Fedora 34 btrfs: failed to read block  groups: -5 open_ctree failed
Date: Mon, 13 Sep 2021 07:58:20 -0400	[thread overview]
Message-ID: <f278527ec652f21aa3b280e9886bc96f@linuxsystems.it> (raw)
In-Reply-To: <98a6a966-cee7-cddd-3c53-fa2e209ed180@suse.com>

Il 2021-09-13 04:05 Qu Wenruo ha scritto:
> For those errors, not even a single dmesg error?

Nope.

> Anyway, if you have most data recovered and have dd copy at hand, then
> you may want to try fully recovery the fs to RW state, by some
> aggressive method:
> 
> # btrfs check --init-extent-tree --repair <dev>
> 
> This command will try to rebuild the extent tree completely, it uses
> existing trees to rebuild, thus requires the fs has nothing else but
> only extent tree corrupted.
> 
> This is *dangerous*, so the final call is still on you.
> But if you really hit no other error messages during the full fs
> recovery, then it looks like only extent tree is corrupted, and may
> worthy a try.
> 
> BTW, since you're already using rescue=nologreplay, you may want to
> zero the log before rebuilding the extent tree.

3 and a half hours later and it's still building the extent tree.
I gave up and made a new fs from scratch.

      reply	other threads:[~2021-09-13 12:14 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
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 [this message]

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=f278527ec652f21aa3b280e9886bc96f@linuxsystems.it \
    --to=darkbasic@linuxsystems.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.