Bug#964818: marked as done (Enable basic subvolume management for rootfs)
Your message dated Fri, 22 Jan 2021 04:48:43 +0000
with message-id <E1l2oNH-0007zE-Tv@fasolo.debian.org>
and subject line Bug#964818: fixed in partman-btrfs 53
has caused the Debian Bug report #964818,
regarding Enable basic subvolume management for rootfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
- To: Debian Bug Tracking System <firstname.lastname@example.org>
- Subject: Enable basic subvolume management for rootfs
- From: Nicholas D Steeves <email@example.com>
- Date: Fri, 10 Jul 2020 16:14:47 -0400
- Message-id: <159441208786.29221.7966431445663142062.reportbug@DigitalMercury.dynalias.net>
Control: patch -1
Control: block 840248 by -1
I have tested the proposed changes and confirmed that they produce the
Briefly, the problem: Installing Debian directly to subvolid 5 rather
than to a "rootfs" (like Fedora) or "@" (like SUSE and Ubuntu)
subvolume causes the following problems:
1. It makes it unreasonably difficult to move to a flat subvolume structure
2. It means that any snapshots of the rootfs creates a nested
subvolume rather than flat subvolume structure.
3. It blocks development of "Boot Environments" (consult the web for how these are used in Solaris and FreeBSD and how these would be useful in Debian).
4. It blocks the ability to stage a system upgrade in a @rootfs-sid or @rootfs-stable+1 subvolume and then pivot into this during a reboot; this is an example of how "boot environments" are useful.
There is precedent in Ubuntu for using a non-configurable method (they
additionally add a "@home" subvolume), and the Ubuntu installer does
not offer user configurability of subvolumes during installation.
My plan is thus:
1. After we have installation to subvolumes, add subvolume listing support to the rescue cd. This has the side-effect of being able to test "boot environments" from the rescue cd.
2. Activate boot environment support via grub-btrfs (#941627).
3. Long-term: add debian-installer support for user-configurable subvolume layout like Fedora and OpenSUSE have. Ideally I'd like to work on this as part of a btrfs-enablement team
CCing Cyril for Kibi ACK :-)
--- End Message ---
--- Begin Message ---
Done: Cyril Brulebois <firstname.lastname@example.org>
We believe that the bug you reported is fixed in the latest version of
partman-btrfs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to email@example.com,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
Cyril Brulebois <firstname.lastname@example.org> (supplier of updated partman-btrfs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing email@example.com)
-----BEGIN PGP SIGNED MESSAGE-----
Date: Fri, 22 Jan 2021 05:35:51 +0100
Maintainer: Debian Install System Team <firstname.lastname@example.org>
Changed-By: Cyril Brulebois <email@example.com>
partman-btrfs (53) unstable; urgency=medium
[ Nicholas D Steeves ]
* Add minimal subvolume support for /. The btrfs volume designated as the
device used for "/" is now configured to use the "@rootfs" subvolume.
This subvolume name was chosen as a compromise between the two primary
conventions in btrfs default subvolume naming. Installing the rootfs to
a subvolume allows update-grub to correctly generate the
"rootflags=subvol=@rootfs" needed to boot from a subvolume, and other
subvolumes may be created as needed. The creation of other commonly used
subvolumes such as "@home" has not been hard-coded, because a user may
choose to locate /home on another device--possibly even on another file
system. This change unblocks development of btrfs boot environments,
which most other major operating systems have supported for quite some
time (Closes: #964818).
* Migrate to debhelper-compat 13.
* Assert Rules-Requires-Root: no.
* Add myself to Uploaders.
b244e3604374e88b488b29bc02efc96789b5ae9d 1682 partman-btrfs_53.dsc
1e4a25f39ad6ef126d1279cd30496addd99d6adc 47260 partman-btrfs_53.tar.xz
95672a6f7c03d4524a451bcf3cbdaf4dc9e9e3b2 5479 partman-btrfs_53_source.buildinfo
df6c3f5af927595dd09e206c3a4a78aa3f4f2a0557bb68e956011e6bf515b6d5 1682 partman-btrfs_53.dsc
010b81a5f6cb2ac51e261b4f924f6adb5a6a4daae09621cb777d8e5d6d85e3fc 47260 partman-btrfs_53.tar.xz
74f4af72e15928b2c283b0088a46997d043b30e067c2d092e47f9368dffe8e2f 5479 partman-btrfs_53_source.buildinfo
dec3d4b785cfe364d3d347a67fb45f8d 1682 debian-installer standard partman-btrfs_53.dsc
02b370b2e7cb05594335cc0ce16e4e78 47260 debian-installer standard partman-btrfs_53.tar.xz
14749f8fa20d6109dd8d090581c44da8 5479 debian-installer standard partman-btrfs_53_source.buildinfo
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
--- End Message ---