mount of nfs fails at boot - Karmic beta

Hello,

Can you also confirm that the NFS filesystems are *not* mounted, before you call 'killall -USR1 mountall'? It's possible to still have the error messages on console but have the mount succeed later once the network interface comes up. What is the output of 'ifconfig'? How is your primary network interface managed - configured in /etc/network/interfaces, managed with network-manager, or managed with something else?

some mount - but never all of the, this time the ones mounted are
192.168.0.2:/mnt/12Gb 13G 9.9G 1.6G 87% /mnt/12Gb
192.168.0.2:/mnt/10Gb 11G 8.8G 930M 91% /mnt/10Gb
192.168.0.2:/mnt/data 54G 52G 2.1G 97% /mnt/data
192.168.0.2:/mnt/music 126G 119G 6.0G 96% /mnt/music

killall -USR1 mountall resulted in all being mounted as I want.

Result of ifconfig

eth0 Link encap:Ethernet HWaddr 00:16:17:13:80:ca
          inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::216:17ff:fe13:80ca/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:900 errors:0 dropped:0 overruns:0 frame:0
          TX packets:953 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:650065 (650.0 KB) TX bytes:144648 (144.6 KB)
          Interrupt:23 Base address:0xda00

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5568 (5.5 KB) TX bytes:5568 (5.5 KB)

Not really sure what you want from the "How is your primary network interface managed -" I did nothing other than install nfs-client, I certainly haven't edited any config files.

This is my /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

Any other information I would be delighted to provide, thanks for looking :)

Ok, your network config looks perfectly normal, so I would expect this to work at this point. Please make sure you've updated to the latest mountall, nfs-common packages in karmic, and edit /etc/init/mountall.conf to change this line:

    exec mountall --daemon $force_fsck $fsck_fix $tmptime

to this:

    exec mountall --debug --daemon $force_fsck $fsck_fix $tmptime > /dev/.udev/mountall.log 2>&1

then reboot, and send the resulting mountall.log file.

Attached is the log file.

I've had a couple of reboots since the updates earlier which included mountall and nfs-common and it appears that the partitions are all being mounted now by the time the desktop is up.

I still get the error messages during boot however.

From the log:

[...]
usr1_handler: Received SIGUSR1 (network device up)
[...]
queue_fsck: /mnt/music: no check required
mounting /mnt/music
spawn: mount -a -t nfs -o rsize=8192,wsize=8192,noexec,nosuid 192.168.0.2:/mnt/music /mnt/music
spawn: mount /mnt/music [1320]
[...]
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mountall: mount /mnt/music [1320] terminated with status 32
mountall: Filesystem could not be mounted: /mnt/music

What version of nfs-common did you have installed when generating this log? This should have been fixed in nfs-common 1:1.2.0-2ubuntu5:

  nfs-utils (1:1.2.0-2ubuntu5) karmic; urgency=low

    * Set upstart jobs to also start on mount attempt, in the event that
      mountall gets to them before the daemons are done starting. Really-fixes
      LP: #431248.

If these error messages are showing up in your latest mountall log, and you're running nfs-common 1:1.2.0-2ubuntu5 or later, then we still have a bug even if your shares all get mounted in the end.

(It's also a bug that the error messages are visible on console, but that's not a bug in nfs-utils; other packages are supposed to take care of hiding those for us during a normal boot.)

nfs-common 1:1.2.0-2ubuntu6

I updated yesterday - including this then rebooted to get the mountall log.

Attached a new mountall.log

sigh - wish I had checked for updates before all of that

nfs-common now nfs-common 1:1.2.0-2ubuntu7

mountall2.log

Thanks for the updated logs. Everything looks as expected in the latest logs, so I think this bug can be closed. As mentioned, the error messages on console will be handled elsewhere.

thank you :)