This drawback has been driving me loopy.
I’ve an NFS server with NFS shares mounted on varied shoppers. Nevertheless, each time I’ve to reboot the NFS server, I invariably find yourself with a bunch of “Stale file deal with” errors on the mounts throughout all my shoppers which forces me to should manually unmount and remount my NFS shares on the shoppers.
I’ve checked my exports on my NFS server with
cat /and so forth/exports and I’m passing the identical fsid for every NFS export throughout reboots.
- How does Business deal with this drawback? I’ve a tough time imagining sysadmins entering into and manually unmounting/remounting every consumer or just restarting related shoppers en masse. Or is that basically how that is dealt with? (Except for the usual, “We by no means have a downtime and we by no means should restart NFS servers.”)
- Why does this occur? Is that this as a result of, regardless that the fsid could be the similar, the NFS server recalculates file handles which might not be the identical throughout reboots?
- Is there one thing I must be doing higher in my mount config to forestall this?
/and so forth/fstab:
[NFSserver]:/mnt/backup /mnt/backup nfs bg,nfsvers=3,tcp Zero 0
Per this submit, it was urged so as to add
intr mount choices, however that does not appear to have made any distinction.
- If all else fails, ought to I simply fall again to utilizing a bash script to observe the mount/listing for a stale file error and have it carry out a umount/mount cycle?