<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - btrfs raid on plain dmcrypt fails to boot randomly" href="https://bugs.freedesktop.org/show_bug.cgi?id=88483#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - btrfs raid on plain dmcrypt fails to boot randomly" href="https://bugs.freedesktop.org/show_bug.cgi?id=88483">bug 88483</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>(In reply to Paolo from <a href="show_bug.cgi?id=88483#c2">comment #2</a>) > 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. Not following. Why does that now work? Can you elaborate? The <a href="show_bug.cgi?id=88483#c1">comment #1</a> is not very clear about that? > /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. Hmm, why do you get the latter three? I mean, the idea is to always use the UUID, and nothing else, not a mixture...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>