Comment 10 for bug 1157171

Revision history for this message
Jarod (jarod42) wrote :

I dug a little deeper and found that only 2 of my 4 NFS Shares were mentioned in the mountall.log.
The /var/log/upstart/statd-mounting*.log for the 2 other filesystems also contained "Terminated" as their only line.

The machine booted 4 times today with no error in the logs so far. So the error is not reproduce-able...

The following might not be directly related to this issue, but some logs under /var/log/upstart show errors multiple times about missing files.:

upstart-socket-bridge.log:
upstart-socket-bridge: Unable to write pid file: No such file or directory
upstart-udev-bridge.log:
upstart-udev-bridge: Unable to write pid file: No such file or directory
ureadahead-other.log:
ureadahead:/var/lib/ureadahead/var.pack: No such file or directory

I think that all of those errors are a result of /var not being mounted when the process is started. /var resides on a separate LV as do /boot, /home, /usr, /var and /tmp.

This is my /etc/fstab:
/dev/mapper/vdrstorage-root / xfs defaults 0 1
UUID=e5f29573-ce86-4f23-9b5f-68f6b1961943 /boot ext4 defaults 0 2
/dev/mapper/vdrstorage-home /home xfs defaults 0 2
/dev/mapper/vdrstorage-tmp /tmp xfs defaults 0 2
/dev/mapper/vdrstorage-usr /usr xfs defaults 0 2
/dev/mapper/vdrstorage-var /var xfs defaults 0 2
/dev/mapper/vdrstorage-swap none swap sw 0 0

192.168.3.42:/mnt/grave/video0 /video0 nfs rsize=32768,wsize=32768,rw,hard,intr,tcp,nfsvers=3,addr=192.168.3.42 0 0
192.168.3.42:/mnt/dvdisos /mnt/dvdisos nfs rsize=32768,wsize=32768,rw,hard,intr,tcp,nfsvers=3,addr=192.168.3.42 0 0
192.168.3.42:/mp3 /mp3 nfs nfsvers=3,rsize=2048,wsize=2048,tcp 0 0
192.168.3.42:/mnt/mplayer /mplayer nfs nfsvers=3,rsize=2048,wsize=2048,tcp