[systemd-bugs] [Bug 88483] btrfs raid on plain dmcrypt fails to boot randomly

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=88483

--- Comment #8 from Kyle <2bluesc at gmail.com> ---
I'm also affected: Arch Linux systemd 221-2 + device-mapper 2.02.122-1 + linux
4.0.7-2

I have 4 physical disks with using LUKS + keyfile and my crypttab uses the
partition's UUID.

The fstab file use the btrfs RAID filesystem's UUID as explained by Lennart
(although using LABEL= appears to behave the same).

The system boots and mounts the filesystem as expected; however, there are 3
pending jobs and the system remains in the "starting" state.

$ systemctl list-jobs
JOB UNIT                     TYPE  STATE  
 72 dev-mapper-crypt3.device start running
 58 dev-mapper-crypt0.device start running
 69 dev-mapper-crypt1.device start running

3 jobs listed.

The missing device crypt2 seems to have worked as suggested to be the device
actually mounted by btrfs magic:

$ systemctl status dev-mapper-crypt2.device
dev-mapper-crypt2.device - /dev/mapper/crypt2
   Follow: unit currently follows state of
sys-devices-virtual-block-dm\x2d6.device
   Loaded: loaded
  Drop-In: /run/systemd/generator/dev-mapper-crypt2.device.d
           └─90-device-timeout.conf
   Active: active (plugged) since Sat 2015-07-04 14:54:08 PDT; 1h 3min ago
   Device: /sys/devices/virtual/block/dm-6

Jul 04 14:54:08 puppies systemd[1]: Found device /dev/mapper/crypt2.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150704/e165637c/attachment.html>