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: add extra points to warn about extra chunk profiles
Date: Thu, 19 Nov 2026 13:50:12 +1030	[thread overview]
Message-ID: <cover.1795057869.git.wqu@suse.com> (raw)

This is inspired by a private user report, that after replacing a
missing device from a degraded RAID1 fs, the fs can no longer tolerate
missing the old good device.

It turns out that during dev-replace, a new system chunk is created, and
since dev-replace destination can not be utilized for chunk allocation,
the new system chunk is SINGLE, thus can no longer tolerate missing that
device.

We need a better solution to this long existing SINGLE-chunk problem,
but for now at least warn the user about this for both balance (success
path) and dev-replace.

Qu Wenruo (2):
  btrfs-progs: always check if the fs has multiple profiles after
    balance
  btrfs-progs: warn about multiple profiles after dev-replace

 cmds/balance.c | 1 +
 cmds/replace.c | 5 ++++-
 2 files changed, 5 insertions(+), 1 deletion(-)

--
2.56.0


             reply	other threads:[~2026-11-19  3:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  3:20 Qu Wenruo [this message]
2026-11-19  3:20 ` [PATCH 1/2] btrfs-progs: always check if the fs has multiple profiles after balance Qu Wenruo
2026-11-19  3:20 ` [PATCH 2/2] btrfs-progs: warn about multiple profiles after dev-replace Qu Wenruo

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.1795057869.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