> Well, we can consider it a wishlist bug that 'cryptsetup isLuks' returns true > in this case; > fixing that isn't actually relevant to resolving the problem you're having.
As the cryptsetup init checks the device with "cryptsetup isLuks" it would actually stop that raid desyncing (i.e. fix the problem). Even if blkid or some confused user continues to throw wrong/arbitrary UUIDs at it. So IMHO its a real bug for cryptsetup upstream. -- breaking raid: root raid_member opened as luks https://bugs.launchpad.net/bugs/531240 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
