touch-packages team mailing list archive

[Roger Binns <ubuntu@xxxxxxxxxxxxxx>]

@pitti:  please can you change the title to something that isn't so
misleading.  That would let others realise this same bug affects them.

With btrfs if you make a filesystem consist of multiple partitions then
each of those partitions will get the same UUID because they are all
parts of the same filesystem.  This is not incorrect behaviour.
PARTUUID and UUID_SUB will be unique per partition as expected, but
those are not what you use in /etc/fstab

I did a fresh install in Virtualbox with a RAID 0 btrfs and @ and @home
subvolumes and it did work.  My real system with considerably more
drives is more complicated.

How do I troubleshoot this?  I need to know what systemd thinks it is
doing and why.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1447879

Title:
  fscking btrfs mount fails with non-unique UUIDs

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have two SSDs in raid0 (striped) configuration with my root and home
  as separate subvolumes.  This setup has worked fine for several Ubuntu
  releases, but fails with systemd on 15.04.  systemd does manage to
  mount root, but then looks like it is trying to fsck the "disk" for
  home which is nonsensical.  After 90 seconds it drops into a useless
  shell where I can't fix things.

  Relevant lines from /etc/fstab

  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /               btrfs   defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@ 0       1
  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home           btrfs   defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home 0       2

  
  Note how the lines are identical except for the subvol value.  I originally didn't have the device= bits either but had to add it for root because of how `btrfs device scan` is run.  With or without it present doesn't make any difference for home.

  There is no such problem booting with upstart

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 23 19:45:38 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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