Skip to contentSkip to conversation

NFS client got stale NFS handle after server reboot

CIRCUMVENTED Reuti 1 participant 1 message Sep 26, 2005

Subsystems (2)
lore
Share & tools
lore

Reuti

author
#0 lore raw

Here one mail, which didn't got to the list by pressing the wrong=20 button. As I just found another fact, first this mail to the list...

Hi Vincent,

one additonal observation:

I looked at /var/lib/nfs/rmtab and was confused by the entries. Seems under the new mode they weren't properly maintained, and also after an unmount some entries stayed there (not all). And there was an additonal line just for the netgroup for each client.

In the legacy mode there is just one entry for each mount, and the machines from netgroups appear there with their nodename. After an unmount the lines are proper removed.

I'm not sure, whether this is important (is rmtab still used in the new mode?) or at least a hint for the source of this behavior - just to let you know.

Best Greetings - Reuti

PS: Yes, in the summary I missed it: it was all under NFSv3.

Quoted 13 lines · Vincent Roqueta

Le jeudi 22 Septembre 2005 16:52, Reuti a =E9crit :
=20

Quoted 11 lines

Finally I could track down the odd behavior (this time in top posting):

If you have this combination:

+ Linux kernel 2.6 nfsd on server
+ 64 bit i386, i.e. x86_64 server
+ using netgroups in /etc/exports
+ operate mountd/exportfs in new mode

you will face the problem of stale NFS handle after a stop/start of of the NFS service. As we want to use 64 bit of course, and enjoy netgroup=

s

Quoted 2 lines
Quoted 2 lines

for easier administration, I got a working setup by *not* mounting /proc/fs/nfsd and forcing this way mountd/exportfs into legacy mode als=

o

Quoted 7 lines
Quoted 3 lines

on a 2.6 kernel.

Cheers - Reuti

=20
=20
=20
There are several problems using x86_64 linux NFS (v4) machines as serv=

er, and=20

Quoted 1 line

it seems to have several problems on 64 bits architectures in general (=

at=20

Quoted 3 lines

least with x86_64 and ppc64. Surely other architectures)
=20
For now there are this issue yet known (linux 2.6.13+CITI, Linux 2.6.14=

-rc*=20

Quoted 2 lines

+CITI)
-> Socket error -11 closing a big file (server : x86_64, clients: x86, =

ppc64)

Quoted 2 lines

-> wrong lock behaviours (Client PPC64, servers: ppc64, x86) -> Input/output error closing a big file (server: ppc64, client x86_64=

)

Quoted 3 lines

-> Oops (Client x86_64, server x86_64) - Linux 2.6.13+CITI =20
However, this issues concern NFSv4. I am going to try to reproduce your=

=20

Quoted 10 lines

problem with NFSv3 and NFSv4.
=20
=20
Vincent
=20
=20
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.=20 Download it for free - -and be entered to win a 42" plasma tv or your v=

ery

Quoted 1 line

own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.p=

hp

Quoted 3 lines

_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs