All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: scrub: small enhancement related to super block errors
Date: Tue,  2 Aug 2022 14:53:01 +0800	[thread overview]
Message-ID: <cover.1659423009.git.wqu@suse.com> (raw)

Recently during a new test case to verify btrfs can handle a fully
corrupted disk (but with a good primary super block), I found that scrub
doesn't really try to repair super blocks.

And scrub doesn't report super block errors in dmesg either.

So this small patchset is to fix the problems by:

- Add explicit error messages for super block errors
- Try to fix super block errors by committing a transaction

Qu Wenruo (2):
  btrfs: scrub: properly report super block errors in dmesg
  btrfs: scrub: try to fix super block errors

 fs/btrfs/scrub.c | 71 ++++++++++++++++++++++++++++++++++--------------
 1 file changed, 50 insertions(+), 21 deletions(-)

-- 
2.37.0


             reply	other threads:[~2022-08-02  6:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  6:53 Qu Wenruo [this message]
2022-08-02  6:53 ` [PATCH 1/2] btrfs: scrub: properly report super block errors in dmesg Qu Wenruo
2022-08-02  6:53 ` [PATCH 2/2] btrfs: scrub: try to fix super block errors Qu Wenruo
2022-08-03 12:55   ` David Sterba
2022-08-03 21:49     ` Qu Wenruo
2022-08-04 13:06       ` David Sterba
2022-08-06  6:01         ` Qu Wenruo
2022-08-06  6:30           ` Qu Wenruo
2022-08-02 14:22 ` [PATCH 0/2] btrfs: scrub: small enhancement related to " David Sterba
2022-08-02 22:18   ` Qu Wenruo
2022-08-03 12:50     ` David Sterba
2022-08-04 14:05 ` David Sterba

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=cover.1659423009.git.wqu@suse.com \
    --to=wqu@suse.com \
    --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 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.