Comment 10 for bug 493480
Revision history for this message
| Swâmi Petaramesh (swami-petaramesh) wrote | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Answer to question in comment 8 : Yes
Answer to comment 9 : As far as I understood, the latest cryptsetup fix (currently in "karmic-proposed), which I have installed on my system (and that didn't help), is for fixing the issue you discuss. It creates the encrypted temp under a temporary device name, mke2fs it, then renames it (using dm_rename or something like that I believe) to its final name.So when the device "appears in the system" under its final name, it supposedly has the filesystem on it.
You say "mountall nevers gives up", so well... I have hard times understanding why the filesystem will mount if I type "mount -a" which will mount all fstab defined filesystems, altough mountall didn't mount it... Unless of course it didn't receive the notification that the device was present... Then wouldn't be "creating it under a temporary name, mke2fs it, then rename it" a good solution ?
Whether or not cryptsetup is to blame, I believe we have something wrong with mountall / upstart anyway, for in the current situation the system will startup with a *mandatory* filesystem unmounted, then daemons start and spit their temp files and sockets into the root filesystem, which is definitely no good.
If for some reason a mandatory FS that mountall *must* mount cannot be mounted, this should be a showstopper for system startup...