batshit insane btrfs installer assume default subvolume is root subvolume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
if you set the default subvolume of a btrfs volume like so
mkfs.btrfs /dev/blasterdisk
mount /dev/blasterdisk /mnt
cd /mnt
btrfs subvolume create foo .
btrfs subvolume set-default foo .
cd ..
umount /mnt
and the install WITHOUT reformatting
then the installer will:
1. create subvolumes foo/@ and foo/@home
2. do no error checking: i.e. if a @ subvolume already exists, lets say you set @ as the default, then the system will install into @, and then the installer will crash while trying to mount @home (when it created @/@home)
while your at it you should also fix upstream, and make it work equally bad with btrfs
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.23
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CasperVersion: 1.305
Date: Tue Mar 20 23:23:09 2012
InstallCmdLine: file=/cdrom/
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcEnviron:
TERM=unknown
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
also, the installer should have a feature to continue where is left off, even if undocumented and hidden