Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, "S ." <sb56637@gmail.com>
Subject: Re: [PATCH] btrfs-progs: rescue: introduce clear-uuid-tree
Date: Mon, 15 Nov 2021 17:33:18 +0100	[thread overview]
Message-ID: <20211115163318.GL28560@twin.jikos.cz> (raw)
In-Reply-To: <3644e6ea-1756-5fd0-106b-2d130f6a2c2b@suse.com>

On Thu, Nov 11, 2021 at 08:37:24AM +0200, Nikolay Borisov wrote:
> On 11.11.21 г. 4:41, Qu Wenruo wrote:
> > [BUG]
> > There is a bug report that a corrupted key type (expected
> > UUID_KEY_SUBVOL, has EXTENT_ITEM) causing newer kernel to reject a
> > mount.
> > 
> > Although the root cause is not determined yet, with roll out of v5.11
> > kernel to various distros, such problem should be prevented by
> > tree-checker, no matter if it's hardware problem or not.
> > 
> > And older kernel with "-o uuid_rescan" mount option won't help, as
> > uuid_rescan will only delete items with
> > UUID_KEY_SUBVOL/UUID_KEY_RECEIVED_SUBVOL key types, not deleting such
> > corrupted key.
> > 
> > [FIX]
> > To fix such problem we have to rely on offline tool, thus there we
> > introduce a new rescue tool, clear-uuid-tree, to empty and then remove
> > uuid tree.
> > 
> > Kernel will re-generate the correct uuid tree at next mount.
> 
> SHouldn't this be made part of btrfs repair, why do we need specific
> rescue subcom ?

This is a one-shot fix for that we have the rescue subcommand, check
could do a normal pass and verify the tree but that's a bit different
what this patch does and requiring --repair goes opposite to what we
recommend to do.

      parent reply	other threads:[~2021-11-15 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  2:41 [PATCH] btrfs-progs: rescue: introduce clear-uuid-tree Qu Wenruo
2021-11-11  2:55 ` Qu Wenruo
2021-11-11  6:37 ` Nikolay Borisov
2021-11-11  6:53   ` Qu Wenruo
2021-11-15 16:33   ` David Sterba [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=20211115163318.GL28560@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=sb56637@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox