Sid can't mount NFS via fstab

[zkab]

I have a Debian (stable) server and some Debian (stable) client and one Debian (unstable) client.
The server is running as a NFS server and exports some files and it is working OK with all my stable clients ... but not with the unstable one. The exported NFS files do not get mounted by fstab when booting.

The /etc/fstab looks like (the same for all stable & unstable ones):

arkiv-x:/home /mnt/Arkiv_X nfs rw,hard,intr,rsize=65536,wsize=65536 0 0

Hmmm ... but when I do a mount with command:

sudo mount -t nfs arkiv-x:/home/ /mnt/Arkiv_X

it gets mounted.

Why can't the unstable client mount NFS with fstab when all the stable ones can ...

[smallchange]

Probably it is not listed in /etc/exports on the server? What kind of message to you get, either on the screen or in /var/log/syslog?

[zkab]

It is listed in /etc/exports on the server ... the unstable client was earlier running as stable (Lenny) and then NFS mount worked OK ... but after upgrading to Sid it can not mount NFS shares from the server ... it is the same computer, same IP-address so nothing is changed on the server
It seems that it has to do with /etc/fstab (I can mount them with 'sudo mount -t nfs arkiv-x:/home/ /mnt/Arkiv_X')
but when I give the command 'sudo mount -a' it stalls and Ihave to ctrl C to get the prompt back
Pls check my attached /var/log/syslog

[smallchange]

The message

Sep 13 17:29:33 zkab if-up.d/mountnfs[eth0]: if-up.d/mountnfs[eth0]: lock /var/run/network/mountnfs exist, not mounting

makes me think that the system is not mounting the export because a lock already exists. Maybe your system crashed? Try removing the lock file and mounting.

Edit: Actually maybe you should check to make sure it is not mounted before you remove the lock.

[zkab]

Is this my problem ?

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390404

[smallchange]

Do you have 2 interfaces? Is the one over which you mount NFS brought up first or last? Do you really care? If you remove the lock file and it mounts and reboots without leaving behind a lock file it was an aberration, possibly from the upgrade. The bug is 3 years old and claims to have been fixed years ago.

[pekka_vanttaukselta]

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390404

Message #17

The output of `sh -x /etc/network/if-up.d/mountnfs' (see below) made it
clear that the lock directory `/var/run/network/mountnfs' was not removed
properly at some point (when it should have been). I manually removed
it, and the script works now. The new question now is, why wasn't the lock
directory removed properly?

I used rm magic to /var/run/network/mountnfs if i remember correctly (myebe not)

and then fstab mount nfs4 shares right in boot.

[zkab]

OK - I removed subdir '/var/run/network/mountnfs' manually and now it mounts NFS shares after reboot

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390404
The new question now is, why wasn't the lock directory removed properly?

This must be a bug