I tried your debugging routine on a second try but could not find the logging output. I don't know where it could have been written, as / was mounting read-only and not getting remounted.
Again I recovered from console 2, this time remounting / rw and then going straight to gdm(which worked and indeed sent me to my LUKS home directory), ignoring the garbage from df /home. df / home reported the tmpfs again-but with the CORRECT percentage used for the LUKS partition shown. Here's what turned up in mtab: /dev/sda1 / ext4 rw,relatime,errors=remount-ro 0 0 proc /proc proc rw 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0 none /sys sysfs rw,noexec,nosuid,nodev 0 0 udev /dev tmpfs rw,mode=0755 0 0 none /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0 none /dev/shm tmpfs rw,nosuid,nodev 0 0 none /var/run tmpfs rw,nosuid,mode=0755 0 0 none /var/lock tmpfs rw,noexec,nosuid,nodev 0 0 none /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0 gvfs-fuse-daemon /home/luke/.gvfs fuse.gvfs-fuse-daemon rw 0 0 /dev/fuse /home/luke/.gvfs fuse rw,nosuid,nodev,user=luke 0 0 tmpfs /mnt/RAMDISK tmpfs rw,size=10% 0 0 /mnt/RAMDISK/.mozilla /home/luke/.mozilla none rw,bind 0 0 RAMDISK now belongs there, as it is now mounted for volatile(secure) web browsing, but mtab does not show /dev/mapper/vg0-home (mounted ANYWHERE), even though it is obviously mounted as I akm using it! This behavior is the exact opposite of the write but not mount behavior I got in the AMD while playing with the script. Again, I suspect some sort of context-sensitive bug in mount itself. If I get such problems with simple scripts, they will make unending trouble in debugging compiled binaries. Mount needs to be fixed, then mountall can be fixed. Meanwhile, that fsck progress support should be added to the existing mountall code so it can be debugged in parallel to the mount bugs, given the tight schedule. Since the changelog for mount doesn't show any likely causes, the underlying trouble has probably been there all along, just waiting for faster routines to trigger them. Here's what's in fstab: # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # / was on /dev/sda1 during installation UUID=c6ecb774-1add-408f-95b2-16d263cadec1 / ext4 relatime,errors=remount-ro 0 1 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 # ####### CHANGES ADDED BY BOOTCRYPT V 1.1 ####### # UUID=8213ad0a-269b-492a-8d30-94b5bac12942 /home ext3 rw,relatime,nofail 0 2 # /home/TMP /tmp ext3 rw,bind,relatime,nofail 0 0 /home/VAR_TMP /var/tmp ext3 rw,bind,relatime,nofail 0 0 /home/VAR_SPOOL /var/spool ext3 rw,bind,relatime,nofail 0 0 /home/VAR_MAIL /var/mail ext3 rw,bind,relatime,nofail 0 0 /home/VAR_CACHE_CUPS /var/cache/cups ext3 rw,bind,relatime,nofail 0 0 UUID=5d09cd8b-61a7-4e86-94f8-c85a406217d7 none swap swap 0 0 > Date: Thu, 8 Oct 2009 02:12:36 +0000 > From: [email protected] > To: [email protected] > 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: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/ -- separate /var and /var/tmp tmpfs dependency loop https://bugs.launchpad.net/bugs/431040 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
