From: Reuti <reuti@staff.uni-marburg.de>
Subject: NFS client got stale NFS handle after server reboot
Date: Tue, 20 Sep 2005 16:36:28 +0200
Message-ID: <43301E6C.3060206@staff.uni-marburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
To: nfs@lists.sourceforge.net
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

Hi all,

I set up a NFS server using kernel NFS in kernel 2.6.11.4-21.9 from 
SuSE. I defined three directories to be exported using netgroups and all 
is working fine, as they can be mounted as intended by all the nodes in 
the cluster.

Up to now I was used to have the NFS feature, that a "hard" mount on the 
nodes will survive a reboot of the NFS server. This is now no longer the 
case. If I reboot the server, all the nodes get a stale NFS handle. I 
can achieve the same effect by simple stopping and starting the nfsd - 
same result.

As we use a RAID card for the disks in the server, I got the idea of 
changing major-minor numbers and also tried to give in the "exports" 
file a chosen "fsid=" for each of the three exports. (Although 
starting/stopping the nfsd won't change the major-minor numbers I 
think.) No change.

Now the funny part: login to a node. Choose any of the three imported 
directories. Make an "umount" and "mount" on this dir - and also the 
other two dirs reappear and are accessible again.

Does anyone has an explanation and/or solution for this setup, to get 
the surviving feature back?

CU - Reuti

(BTW: all partitions are ext2 on x86 machines)


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs