/var on separate partition fails at boot time
Bug #555780 reported by
Krzysztof Matusik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: initramfs-tools
The problem is having /var on separate partition.
I suppose initramfs' initrd generation script can't handle the situation properly.
If I put /var separately in /etc/fstab (with correct copy of direcory tree of course) resulting system fails to boot.
This can be /var/run and /var/lock mounted during the initramfs boot phase mounted to root ( / ) tree instead of /var tree.
Therefore /var, if exists in fstab, should be mounted before /var/run and /var/lock in initramfs boot phase. Or /var/run and /var/lock should be binded to newly mounted /var again, somewhere at the end of boot phase. Well, I don't know the initramfs-tools so good...
rgs
Changed in initramfs-tools (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
I've investigated the issue and it looks it's not a initramfs-tools package problem but mountall problem.
There is a file /lib/init/fstab from that package that has configuration lines with /var/run and /var/lock.
It seems that one who has /var on separate partition should put lines for 'run and 'lock in his /etc/fstab to override the /lib/init/fstab lines.
There should be some documentation, guide for users- then this "bug" would be partially solved.