From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: docs: discourage root btrfs usage without an initramfs
Date: Mon, 14 Sep 2026 19:18:31 +0200 [thread overview]
Message-ID: <20260914171831.GP54722@twin.jikos.cz> (raw)
In-Reply-To: <c0fbd931a33a130a51f215fc0712954edb18b654.1789205131.git.wqu@suse.com>
On Sat, Sep 12, 2026 at 06:55:32PM +0930, Qu Wenruo wrote:
> For multi-device btrfs, device scanning is required before mounting, and
> without an initramfs it's impossible to mount a multi-device btrfs.
>
> Even if the rootfs is a single-device btrfs, there is nothing preventing
> the end user to add a device to that btrfs, and fail the next boot.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
> Documentation/mkfs.btrfs.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/mkfs.btrfs.rst b/Documentation/mkfs.btrfs.rst
> index 0d3d6051b0e7..0bc7b7ac3808 100644
> --- a/Documentation/mkfs.btrfs.rst
> +++ b/Documentation/mkfs.btrfs.rst
> @@ -346,6 +346,10 @@ devices to scan at the time of mount.
> before all block devices are discovered. The waiting is usually done on the
> initramfs/initrd systems.
>
> + Thus using btrfs as a rootfs without an initramfs is not recommended.
> + Adding a new device to the rootfs can easily cause the next boot to fail, as
> + there is no way to register all devices prior to mounting.
That's not a good placement, we should write a full section how to use
btrfs without initrd and what are the caveats. A paragraph burried in
mkfs will probably never got noticed.
> +
> .. warning::
> RAID5/6 has known problems and should not be used in production.
>
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-09-14 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 9:25 [PATCH] btrfs-progs: docs: discourage root btrfs usage without an initramfs Qu Wenruo
2026-09-14 17:18 ` David Sterba [this message]
2026-09-14 21:28 ` 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=20260914171831.GP54722@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--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