Comment 21 for bug 431040

  I just tried this on the Intel Atom(the less buggy of my two machines about boot mount) and it was a huge flop. I did not use the "debug" you mentioned, having not seen it yet, but it refused to remount / rw, leaving it read-only. My /dev/mapper/vg0-home (LUKS) partition did not mount-and calling df /home showed /mnt/RAMDISK/.mozilla instead of /dev/mapper/vg0-home-even though the /mnt/RAMDISK tmpfs for Firefox isn't even in my fstab, nor mounted at boot. Needless to say, X won't open that way, so I recovered from vt2.

For now, I have thrown in the towel on the mountall binary and have been playing with scripts. I use a single mountall script (your mountall.conf file works fine and is in fact the same as what I wrote except what I commented out you removed) to mount all the stuff in fstab.

I have been playing with the attached script for days, and have gotten it to the point of having it's own fsck recovery shell from which booting can actually proceed bypassing checks if necessary, and indicating forced checks(by mount count ONLY) through usplash write. For some reason, I cannot get console output with echo in a script run at that stage on ANY vt! Therefore, all log messages depend on usplash set verbose-and I use a lot of them for debugging. Without terminal output, getting progress indication of forced checks has been beyond me, so I have set the 140+GB home partition not to force checks unless marked dirty.

Interestingly, mount itself seems buggy, sometimes writing to mtab on the AMD 64(with 32 bit Ubuntu), but NOT the Intel Atom, that it has mounted the LUKS partition while in fact the root partition's mount point comes up on opening.

Sometimes mount -a will work right, sometimes not. The attached script calls mount -a twice in an effort to run the bind mounts last(I found a better way to exclude the binds on first run but it didn't help the AMD) so it does not get confused-but due to mount bugs on the AMD I had to hardcode the home partition for it. I could write code to parse this, but that version is in only one machine. The script as attached is what I am using on the Intel atom.

Maybe some of the bugs plaguing the mountall binary are actually mount bugs?
Anyway, with Beta out and the release just weeks away, I hope there is a backup plan.

> Date: Thu, 8 Oct 2009 02:12:36 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 431040] Re: separate /var and /var/tmp tmpfs dependency loop
>
> I've uploaded a new mountall package to the ubuntu-boot PPA:
>
> https://launchpad.net/~ubuntu-boot/+archive/ppa
>
> I would appreciate it if you could install this and try it out.
> *BEFORE* you reboot though, could you run "sudo mountall --debug >
> mountall.log 2>&1" and attach that to this bug - then after you reboot,
> let me know whether it worked or not.
>
> Thanks
>
> --
> separate /var and /var/tmp tmpfs dependency loop
> https://bugs.launchpad.net/bugs/431040
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/