Comment 7 for bug 571682

Yes, this is some kind of race condition. Scott, I am not sure if you are aware that in the above setup, the volumes are initialized each time with a random key, and the filesystem (tmp) / swapspace signature is recreated each time on boot. It seems mountall is not prepared for that and waits for the device to become ready, but not for the filesystem/swap signature to be created. If I change the setup to a fixed-keyfile one, where the filesystem is not recreated each time, everything works.

This is a kind of race condition, as it occurs only sometimes on faster (dual-core) machines, but nearly always on slower (single-core) machines. Obviously, on the faster machine, the crypttab handling process manages to get everything done before mountall tries to mount, on the slower one it does not.