subiquity isn't able to create btrfs subvolumes during installation
Bug #1881932 reported by
Gannet
This bug affects 16 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
New
|
Undecided
|
Unassigned | ||
subiquity |
Triaged
|
Undecided
|
Unassigned | ||
ubuntu-desktop-installer |
New
|
Undecided
|
Unassigned |
Bug Description
I always use my system on two btrfs subvolumes: @ and @home. And it worked until 20.04 came out with no Debian installer but with new unusable subiquity one which is not creates btrfs subvolumes if I chose / as a mount point on btrfs. Instead of it says: "Mounting an existing filesystem at / is usually a bad idea, proceed only with caution" which is quite strange in my case. How should I install 20.04 on btrfs with two subvolumes?
no longer affects: | subiquity (Ubuntu) |
tags: | added: focal |
tags: | added: subiquity |
tags: | added: wos |
tags: | removed: subiquity wos |
tags: | added: subiquity |
To post a comment you must log in.
Yes, this is a gap.
Out of curiosity, would you be OK with supporting ZFS in a similar way as the desktop installer currently does, or do you prefer btrfs for some reason?