Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: check: add repair ability for missing root orphan item
Date: Sat, 15 Nov 2025 08:15:58 +1030	[thread overview]
Message-ID: <cover.1763156743.git.wqu@suse.com> (raw)

There is another report of missing root orphan item, although the latest
btrfs-progs can detect such corruption, we have no way to fix it.

This makes the affected end users helpless, as the corruption can happen
for affected old kernels, and that damage is persistent.

Add the repair ability to save those affected end users.


Qu Wenruo (2):
  btrfs-progs: check: add repair ability for missing orphan root item
  btrfs-progs: fsck-tests: make test case 066 to be repairable

 check/main.c                                  |  5 +++
 check/mode-common.c                           | 33 +++++++++++++++++++
 check/mode-common.h                           |  1 +
 check/mode-lowmem.c                           | 13 ++++++--
 .../.lowmem_repairable                        |  0
 .../066-missing-root-orphan-item/test.sh      | 14 --------
 6 files changed, 49 insertions(+), 17 deletions(-)
 create mode 100644 tests/fsck-tests/066-missing-root-orphan-item/.lowmem_repairable
 delete mode 100755 tests/fsck-tests/066-missing-root-orphan-item/test.sh

--
2.51.2


             reply	other threads:[~2025-11-14 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 21:45 Qu Wenruo [this message]
2025-11-14 21:45 ` [PATCH 1/2] btrfs-progs: check: add repair ability for missing orphan root item Qu Wenruo
2025-11-19 23:02   ` Boris Burkov
2025-11-14 21:46 ` [PATCH 2/2] btrfs-progs: fsck-tests: make test case 066 to be repairable Qu Wenruo
     [not found]   ` <314461b6-9c30-4f19-aed3-486656db661e@libero.it>
2025-11-15 10:45     ` Qu Wenruo
2025-11-19 23:03   ` Boris Burkov

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.1763156743.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox