[Fwd: Re: NFS problems across reboot]
Subsystems (2)
Neil --
Quoted 3 lines
From: Neil Brown <[email protected]>
My guess is that "exportfs -a" is being run *After* rpc.nfsd. It must must run *before* for correct operation.
I did not know this. Can you explain why?
Our situation -- We run a proprietary file system that holds the exported directories, but it does not start up until _after_ nfs is started. On a reboot, we run "exportfs -a" again after our file system is up, so the clients that held mounts before the reboot don't get stale file handle errors. (The first run of exportfs, before rpc.nfsd, did not find the exported directories since the file system they are on was not up yet.)
Will this be a problem? Should we delay starting nfs until _after_ our file system is up?
We are still having some problems with stale file handles on reboot, even after the second exportfs, but it only happens occasionally. Sometimes it goes away after a minute or two, sometimes not.
We are running 2.4.17 on both clients and servers.
Thanks for any info on this,
-- Al
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 7 lines · On Sunday April 7, [email protected] wrote:
Neil --
Quoted 3 lines
From: Neil Brown <[email protected]>
My guess is that "exportfs -a" is being run *After* rpc.nfsd. It must must run *before* for correct operation.I did not know this. Can you explain why?
If a NFS request arrives after nfsd is started, and before exportfs is run, the server will return "ESTALE". The client will think that it's filehandle is stale and will fail all future accesses. Even if it only failed this one access, it would still be a problem.
So you could not start the nfsd until all exported filesystems have been mounted and exported.
This will not always manifest as a real problem: it depends on how hard the clients are hitting the server and how small the window is between starting nfsd and exporting the filesystems, but it certainly can be a problem.
Quoted 11 lines
Our situation -- We run a proprietary file system that holds the exported directories, but it does not start up until _after_ nfs is started. On a reboot, we run "exportfs -a" again after our file system is up, so the clients that held mounts before the reboot don't get stale file handle errors. (The first run of exportfs, before rpc.nfsd, did not find the exported directories since the file system they are on was not up yet.)
Will this be a problem? Should we delay starting nfs until _after_ our file system is up?
It would be best if you did.
NeilBrown
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs