Skip to contentSkip to conversation

nfs4 client not surviving server reboot

DISCUSSION Brian J. Murrell 2 participants 2 messages Jun 4, 2009 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi all,

A couple of times now I have (unforunately) needed to reboot the NFS server here and my one NFS4 client is simply not recovering that incident and needs to be rebooted as well.

The particulars are:

NFS Server:
-----------
Ubuntu Hardy running kernel 2.6.24-23-generic

NFS Client:
-----------
Ubuntu Jaunty running kernel 2.6.27-12-generic

The filesystems mounted are:

# grep linux: /proc/mounts
linux:/home/share /autohome/share nfs4 rw,vers=4,rsize=8192,wsize=8192,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0
linux:/usr/local /usr/local nfs4 rw,vers=4,rsize=32768,wsize=32768,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0
linux:/mnt/data /data nfs4 rw,vers=4,rsize=32768,wsize=32768,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0
linux:/mnt/mp3 /mnt/mp3 nfs4 rw,vers=4,rsize=32768,wsize=32768,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0

I don't really know where to even start trying to figure this one out. Ideas?

b.

A message that is not in the archive (sent off-list or not yet received): 1244138569.8469.26.camel-lA68w17JHpfIgqYUaR6mlLDks+cytr/[email protected]

#2 lore raw
Quoted 18 lines · Brian J. Murrell

Hi all,

A couple of times now I have (unforunately) needed to reboot the NFS server here and my one NFS4 client is simply not recovering that incident and needs to be rebooted as well.

The particulars are:

NFS Server:
-----------
Ubuntu Hardy running kernel 2.6.24-23-generic

NFS Client:
-----------
Ubuntu Jaunty running kernel 2.6.27-12-generic

The filesystems mounted are:

Quoted 8 lines
# grep linux: /proc/mounts
linux:/home/share /autohome/share nfs4 rw,vers=4,rsize=8192,wsize=8192,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0
linux:/usr/local /usr/local nfs4 rw,vers=4,rsize=32768,wsize=32768,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0
linux:/mnt/data /data nfs4 rw,vers=4,rsize=32768,wsize=32768,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0
linux:/mnt/mp3 /mnt/mp3 nfs4 rw,vers=4,rsize=32768,wsize=32768,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=10.75.22.1,addr=10.75.22.3 0 0

I don't really know where to even start trying to figure this one out. Ideas?

A dumpo of any relevant syslog entries would help, as would a packet trace of the traffic between client and server (e.g. 'tcpdump -s 90000 -w /tmp/dump.out host <myserver> and port 2049'.

Trond