batshit insane btrfs installer assume default subvolume is root subvolume

Bug #960894 reported by shawnlandden on 2012-03-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

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
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
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/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
 PATH=(custom, no user)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

shawnlandden (shawnlandden) wrote :
shawnlandden (shawnlandden) wrote :

also, the installer should have a feature to continue where is left off, even if undocumented and hidden

shawnlandden (shawnlandden) wrote :

the ideal fix for this is to detect the default subvolume (and perhaps expose it in the interface) and then make the new subvolume childs of that (as it currently does) and then actually properly handle these new subvolumes (broken)

Exception during installation:
Mar 21 06:22:44 ubuntu Traceback (most recent call last):
Mar 21 06:22:44 ubuntu File "/usr/share/ubiquity/", line 1690, in <module>
Mar 21 06:22:44 ubuntu
Mar 21 06:22:44 ubuntu File "/usr/share/ubiquity/", line 55, in wrapper
Mar 21 06:22:44 ubuntu func(self)
Mar 21 06:22:44 ubuntu File "/usr/share/ubiquity/", line 166, in run
Mar 21 06:22:44 ubuntu self.configure_face()
Mar 21 06:22:44 ubuntu File "/usr/share/ubiquity/", line 271, in configure_face
Mar 21 06:22:44 ubuntu uid = int(uid)
Mar 21 06:22:44 ubuntu ValueError: invalid literal for int() with base 10: ''
Mar 21 06:22:44 ubuntu

tags: added: installer-crash
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 960894

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers