[DRBD-user] Stale NFS file handle vs. NFS-Server-README.txt

Peter Kruse pk at q-leap.com
Wed Jun 9 14:36:55 CEST 2004

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Eugene Crosser wrote:
>>I'm trying to set up a drbd+heartbeat NFS-server. Most things work fine,
>>but if I write to the NFS storage during failover, I get a Stale NFS
>>file handle error:
>>root:~> cp /tmp/large_file /mnt
>>cp: writing `/mnt/large_file': Stale NFS file handle
>>cp: closing `/mnt/large_file': Stale NFS file handle

I don't see what's wrong with that, the service is unavalaible
for the time the failover takes place.  It should recover when
the nfs service is available again, when the rmtab (see below) file
contains the client information for this filesystem on the other node.

> Not sure if it will help in your particular case, but I have two pieces
> of advice:
> - do *not* ever unexport the filesystem when you stop NFS server
> - keep /var/lib/nfs in the exported filesystem (e.g. symlink there)

I've seen this suggestion several times, and I don't know who came
up with this ... idea.  What are going to do in an active/active
Cluster?  What if one node fails over to the other?  Better is to
keep /var/lib/nfs where it is and merge information to the
rmtab file.  This is how we do it anyways.



More information about the drbd-user mailing list