Bug#1017762: incompatible after "btrfs subvolume set-default ..."
Source: partman-btrfs
Version: 55
Severity: normal
It is great to have btrfs support with @rootfs. Thanks. I wish if it
is a bit more verbose on what it does in installer dialogue. This is
more important if we want to use existing btrfs with something like
@home-uid1000 in it ;-)
Anyway, I experienced an unsuccessful install to the existing btrfs
partition. I had @rootfs-broken-backup in it and I set "btrfs subvolume
set-default ..." to it. Don't ask me why I did. But this caused d-i
to stop installation without much error report.
EXPECTED BEHAVIOR:
1. Clearly mention the use of subvolume @rootfs in d-i dialogue.
(This is for both fsck or fsck-less install cases.)
2. Check "btrfs subvolume get-default <btrfs-partition>" to be "ID 5
(FS_TREE)". If not,
* stop installation with clear message or (reasonable?)
* set-default to fix this. (better?)
(This is for fsck-less install)
3. Check existance of @rootfs. If exists,
* stop installation with clear message or (simple)
* make a backup snapshot of @rootfs to some other name and
remove @rootfs to have clean start. (better)
(This is for fsck-less install)
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: