Attached is a mountall --debug log corresponding to the following setup in karmic, using cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7.1:
$ grep crypttmp /etc/fstab /dev/mapper/crypttmp /tmp ext2 defaults 0 0 $ grep crypttmp /etc/crypttab crypttmp /dev/sda8 /dev/urandom tmp $ Key lines are: try_mount: /tmp waiting for device /dev/mapper/crypttmp update_mount: /tmp: /dev/mapper/crypttmp_unformatted ext2 defaults mounted: /tmp But at the end, mountall has exited and /tmp is *not* mounted. So there are two issues here. 1) mountall thinks /tmp is mounted when it isn't. That looks like a mountall bug to me, and I think should be tracked in this bug report. 2) Now instead of seeing the device before it has a filesystem on it, mountall sees the device before the device node is under its final name. This indicates the fix for bug #475936 is incomplete, so I'll mark that bug as verification-failed for SRU. Unfortunately, I'm not sure how to fix this; if 'dmsetup rename' isn't a reliable way to expose the device to mountall under the new name, I don't know what will be. Scott, if you can provide any insight into a correct means of notifying mountall that the filesystem is created and ready for mounting, I would appreciate it. ** Attachment added: "mountall.log" http://launchpadlibrarian.net/37066442/mountall.log ** Package changed: cryptsetup (Ubuntu) => mountall (Ubuntu) -- [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
