Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: "Dāvis Mosāns" <davispuh@gmail.com>, linux-btrfs@vger.kernel.org
Cc: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: Allow read-only mount with corrupted extent tree
Date: Wed, 11 Aug 2021 16:41:02 -0400	[thread overview]
Message-ID: <ccd23bbb-1404-0727-383f-2412a5d4df36@toxicpanda.com> (raw)
In-Reply-To: <20210811200717.48344-1-davispuh@gmail.com>

On 8/11/21 4:07 PM, Dāvis Mosāns wrote:
> Currently if there's any corruption at all in extent tree
> (eg. even single bit) then mounting will fail with:
> "failed to read block groups: -5" (-EIO)
> It happens because we immediately abort on first error when
> searching in extent tree for block groups.
> 
> Now with this patch if `ignorebadroots` option is specified
> then we handle such case and continue by removing already
> created block groups and creating dummy block groups.
> 

Already done and queue'ed up for the next release

btrfs: rescue: allow ibadroots to skip bad extent tree when reading block group 
items

thanks,

Josef

  reply	other threads:[~2021-08-11 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 20:07 [PATCH] btrfs: Allow read-only mount with corrupted extent tree Dāvis Mosāns
2021-08-11 20:41 ` Josef Bacik [this message]
2021-08-12 17:18   ` Dāvis Mosāns
  -- strict thread matches above, loose matches on Subject: below --
2021-03-17  1:20 [RFC] " Dāvis Mosāns
2021-03-21 21:49 ` [PATCH] " Dāvis Mosāns
2021-04-21 16:00   ` Dāvis Mosāns

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=ccd23bbb-1404-0727-383f-2412a5d4df36@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=clm@fb.com \
    --cc=davispuh@gmail.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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