Hi All,
Thanks to following people for their quick response:
Richard Bemrose: rb237_at_phy.cam.ac.uk
Lucio Chiappetti: lucio_at_ifctr.mi.cnr.i
Leon Troeth : lanks_at_yoyo.cc.monash.edu.au
Knut Helleb :Knut.Hellebo_at_nho.hydro.com
Answers:
*** I believe this is caused by deleting a temporary NFS file lock which was
created by some program while the program is still running. For example:
/some/dir/path/.nfsB64C001
Rich
*** This sort of message should mean that the remote machine from which the
disk
is mounted is unavailable, while the local machine has still the disk
mounted.
Or that the disk became unavailable and the local machine did not notice
when
it became available again.
Make sure the remote machine is available, then dismount (or dismount and
re-mount) the affected disks. Make sure disks are really unmounted
(eventually
issue umount command more than once) looking at the "df" output
Lucio Chiappetti
*** For us that happens when the other machine has rebooted. eg, machine A
nfs mounts a directory from machine B. Machine B is rebooted. Then
machine A gets the stale file handle errors.
Just unmount and then remount the partition on machine A.
Leon
*** The errormessage only indicate that the client opened a file that
subsequently have been deleted by another client (or the server itself)
before the client closed the file.
Knut
Regards,
Erkan Durmus
ISIK Insurance Co.
Received on Fri Feb 20 1998 - 17:31:06 NZDT