[Bug 960894] Re: batshit insane btrfs installer assume default subvolume is root subvolume

shawnlandden 960894 at bugs.launchpad.net
Wed Mar 21 06:33:52 UTC 2012


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)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/960894

Title:
  batshit insane btrfs installer assume default subvolume is root
  subvolume

Status in “ubiquity” package in Ubuntu:
  New

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)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/960894/+subscriptions




More information about the foundations-bugs mailing list