This content has been marked as final. Show 4 replies
The problem usually appears when a NFS mount was removed while a client still holds an active reference to a file handle, for instance if the NFS server crashed while copying a file. Your options to correct the issue will depend on NFS version and how you initially mounted the NFS share. NFS mounting options like soft, hard and intr will influence your available options.
If you hard mounted a NFS share, you may need to reconnect the NFS share in order for the NFS client to resume its operation, then disconnect the client. In the worse case you may have to reset the computer to clear stalled NFS file handles.
if you are on linux (what I assume)
sudo umount -l /mnt/ftpd002
Thanks! Here are the options on the mount...it was hard mounted. So our only options, then, are to a) see if the NFS share can be remounted or b) reset?
192.xxx.xxx.xx:/home/pasftp /mnt/ftpd002\040(deleted) nfs4 rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.xxx.xxx.xx,minorversion=0,local_lock=none,addr=192.xxx.xxx.xx 0 0
Alvaro - The -l also gives the same error.
What's the output of
sudo lsof | grep '/mnt/ftpd002'