Comment 13 for bug 493480

I think that Scott James Remnant has hit the nail on the head in comment #9. dm-crypt creates encrypted block devices, which are transparent to the system. So what happens is something like this:

1. dm-crypt creates an encrypted block device, and mounts it to /dev/mapper/ctmp.
2. dm-crypt then runs mkfs.ext2 on /dev/mapper/ctmp.
3. mountall wakes up and sees the device it has been waiting for exits, and tries to mount it. Either step 2 hasn't started yet or hasn't finished yet, and so the mount fails.

I get the following output when my system boots, which makes me believe the above is the case:

* ctmp (starting)
mount: /dev/mapper/ctmp already mounted or /tmp busy
mountall: mount /tmp [1004] terminated with status 32
mountall: Filesystem could not be mounted: /tmp
init: mountall main process (488) terminated with status 4
Mount of root filesystem failed.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and reboot the system.
* ctmp (started)... [ OK ]