Package: nfs-common
Version: 1:1.2.3-2

After the upgrade from squeeze to testing the NFS3 mounts
are ignored at boot time. Instead I see a message

rpcbind:
Cannot open '/var/run/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such 
file or directory)
rpcbind: Cannot open '/var/run/rpcbind/portmap.xdr' file for reading, errno 2 
(No such file or directory)

If I login as root and do a "mount -a" manually, then the
NFS3 file systems are mounted, but of course I would prefer if
this could happen automagically.

NFS4 is not affected by this problem, as it seems. Here is
/proc/mounts after "mount -a":

nfs-storage:/storage/ /storage nfs4 
rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.19.97.183,minorversion=0,local_lock=none,addr=172.19.96.213
 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
nfs-data:/space/data /data nfs 
rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.19.96.215,mountvers=3,mountport=49269,mountproto=udp,local_lock=none,addr=172.19.96.215
 0 0
nfs-home:/space/home /home nfs 
rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.19.96.215,mountvers=3,mountport=49269,mountproto=udp,local_lock=none,addr=172.19.96.215
 0 0


My old squeeze configuration used portmap (I checked the
backup).

Is this related to introducing /run in tmpfs?


Regards

Harri



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4df0c364.4040...@aixigo.de

Reply via email to