Perhaps a silly question, but at the point that /dev/mapper/c_tmp is announced to the system - does it have a filesystem on it?
If cryptsetup doesn't call mke2fs until after creating the dm device with that name, then udev is told about the block device before the filesystem is created, so blkid returns no filesystem, so mountall will ignore it (if it didn't ignore it - it would fail to mount anyway). (The two suggested workarounds would introduce enough of a delay that it might get away with it.) This still leaves it as a cryptsetup bug, for announcing a block device without a filesystem and not following up with a "change" event when the block device is ready. -- [Karmic, security] Encrypted /tmp no longer mounting after upgrade to karmic https://bugs.launchpad.net/bugs/493480 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
