[Bug 1242909] Re: Mountall doesn't seem to wait for /home (btrfs on luks enc volume) during boot

[Steve Langasek]

You must not use UUIDs to identify DM devices (such as LUKS devices) in
/etc/fstab; you must use devicemapper names instead, as these are the
only things that are guaranteed to be stable and unique.  (A UUID is
*not* unique on DM, thanks to snapshotting.)

What's actually happening here is that cryptsetup opens the device first
under a temporary name, then moves it into its final name once it's done
with setup; but mountall sees the udev events in between and tries to
mount it under the temporary device name, which disappears before it can
do anything with it.  So mounting by DM name fixes this problem.  The
cryptsetup behavior exists mostly to handle swap partitions that have to
have mkswap run before they're exposed up the stack, but even though we
could change cryptsetup's behavior to not break when UUIDs are used in
/etc/fstab, the other problems with using UUIDs are significant enough
that this we're not going to invest the time in making this work.

BTW, your fstab shows that you have /home marked 'bootwait'.  You've
probably noticed this doesn't help.  You can drop that, it's a no-op for
the /home partition. :)

** Changed in: mountall (Ubuntu)
       Status: New => Invalid

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

Title:
  Mountall doesn't seem to wait for /home (btrfs on luks enc volume)
  during boot

Status in “mountall” package in Ubuntu:
  Invalid

Bug description:
  My /home is a btrfs filesystem in a luks volume.

  While booting I am asked for the password, but after entering the
  password am told /home failed to mount

  I log in as root and issue mount /home

  so cryptsetup luksOpen is correctly called as per my /etc/crypttab

  This doesn't appear to me to be the same as bug #1159256

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: mountall 2.52
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 21 17:00:56 2013
  InstallationDate: Installed on 2013-10-19 (2 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=516da155-13dc-434d-bf21-22eccaba39e3 ro rootflags=subvol=@ quiet splash
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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