[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 #2 from Paolo <palmaway at gmx.it> ---
Hi, and thanks for your reply. However, putting the UUID in fstab doesn't work
on my system, as mentioned in the original bug report above. Here are a few
additional info:

The relevant blkid output:

/dev/mapper/cryptb: LABEL="data" UUID="ee0726c7-f7d1-4031-8a53-32d384334196"
UUID_SUB="8eb20b58-f736-404d-92dd-bb467da8a275" TYPE="btrfs"
/dev/mapper/cryptc: LABEL="data" UUID="ee0726c7-f7d1-4031-8a53-32d384334196"
UUID_SUB="0072ff4d-25e6-44a1-9fae-8cb9b38299d9" TYPE="btrfs"
/dev/mapper/crypta: LABEL="data" UUID="ee0726c7-f7d1-4031-8a53-32d384334196"
UUID_SUB="d0a0ff7f-76d0-4572-9e0f-db9f20ea6fa0" TYPE="btrfs"

My /etc/crypttab:

crypta  /dev/sda  /root/key.crypta  cipher=aes-xts-plain64,size=512,hash=plain
cryptb  /dev/sdb  /root/key.cryptb  cipher=aes-xts-plain64,size=512,hash=plain
cryptc  /dev/sdc  /root/key.cryptc  cipher=aes-xts-plain64,size=512,hash=plain

The relevant part of my /etc/fstab:

/dev/mapper/cryptc  /data  btrfs 
defaults,device=/dev/mapper/crypta,device=/dev/mapper/cryptb,device=/dev/mapper/cryptc,compress-force=lzo
 0 0

Again, if I put in the fstab the UUID shared by the btrfs raid filesystem
indicated by blkid (ee0726c7-f7d1-4031-8a53-32d384334196) then the problem is
not solved, it actually gets worse, as indicated in the original report above!
I get 3 "start job" messages, one related to the /dev/disk-by-uuid and the two
relative to the remaining devices /dev/mapper/cryptX.

-- 
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/20150209/3e68a615/attachment.html>