[Bug 139230] Re: /var is mounted too late during the init sequence
Sadly the fault here is in the FHS, which specifies that those two directories are under /var -- we need files in both directories to be able to mount /var, so it's a bit of a chicken and egg situation. The Ubuntu solution is reasonably elegant (bind-mount so that /var/run and /var/lock are available whether you mount or unmount /var -- but it means a little bit of extra work to set it up. A recent fix went in that creates these directories on the root filesystem on shutdown if they don't already exist, this should solve 95% of the problem since after adding a /var, you'll reboot and it'll take care of putting in the necessary mount points ** Changed in: sysvinit (Ubuntu) Status: Incomplete = Fix Released -- /var is mounted too late during the init sequence https://bugs.launchpad.net/bugs/139230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139230] Re: /var is mounted too late during the init sequence
** Changed in: upstart (Ubuntu) Assignee: (unassigned) = Scott James Remnant (keybuk) -- /var is mounted too late during the init sequence https://bugs.launchpad.net/bugs/139230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139230] Re: /var is mounted too late during the init sequence
I'm sorry, but I am unable to replicate this bug; in order to help debug it, you will need to provide more information. The test setup I used had two 8GB SCSI drives, partitioned as follows: /dev/sd[ab]1 - md0 - /boot /dev/sd[ab]2 - swap /dev/sd[ab]5 - md1 - LVM PV LVM is configured with a single VG (UbuntuVG) with two LVs (root and var) /dev/mapper/UbuntuVG-root (actually its UUID) is mounted on / /dev/mapper/UbuntuVG-var (actually, its UUID) is mounted on /var The system responds as I would expect. /var/run and /var/lock are mounted early on the stub mountpoints that the installer creates on the root filesystem for this purpose (so the root has /var, /var/run and /var/lock directories). Then during mountall, these are bind-mounted in /dev/shm so that other filesystems can be mounted over the top; once mount -a has completed (ie. the new /var is in place), the filesystems from /dev/shm are move- mounted back into /var/run and /var/lock which may now be on a different filesystem. The problem *may* be simply caused by a missing /var/run and /var/lock on the root filesystem, which will prevent these mountpoints existing at all! Could you describe the symptoms that this problem causes you? If you're running gutsy, ensure you are up to date. The latest initscripts package (2.86.ds1-14.1ubuntu30) contains a fix that makes sure that these mount targets exist on the root filesystem (by creating them on shutdown before it's mounted read-only, but after other filesystems are mounted). ** Changed in: sysvinit (Ubuntu) Sourcepackagename: upstart = sysvinit Status: Confirmed = Incomplete Target: ubuntu-7.10-rc = None -- /var is mounted too late during the init sequence https://bugs.launchpad.net/bugs/139230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139230] Re: /var is mounted too late during the init sequence
Yes, the problem is that you have to create /var/lock, /var/run in root filesystem - even though you have /var as a separate filesystem. It is confusing. Especially so for the people who initially do not have /var as separate filesystem and decide at some point separate it. They have to be very careful and keep /var/lock, /var/run on the root filesystem (while having them ALSO on /var filesystem). It is not transparent, don't you think? -- /var is mounted too late during the init sequence https://bugs.launchpad.net/bugs/139230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139230] Re: /var is mounted too late during the init sequence
** Changed in: upstart (Ubuntu) Target: ubuntu-7.10-beta = ubuntu-7.10-rc -- /var is mounted too late during the init sequence https://bugs.launchpad.net/bugs/139230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139230] Re: /var is mounted too late during the init sequence
marked my bug 134650 as a dupe to this one. There is some info in there which might be interesting. This problem had broken networking for me. -- /var is mounted too late during the init sequence https://bugs.launchpad.net/bugs/139230 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
