Learn how to resolve mount. This is a Network File System error that can be resolved from the client or server end. When you are using the Network File System in your environment, you must have seen mount. This error denotes that the NFS share is unable to mount since something has changed since the last good known configuration.
Whenever you reboot the NFS server or some of the NFS processes are not running on the client or server or share is not properly exported at the server; these can be reasons for this error. Because this means the configuration part is correct since it was previously mounted.
Asked 7 years, 5 months ago. Active 1 year ago. Viewed 94k times. Any way to fix that? Improve this question. Add a comment. Active Oldest Votes. Improve this answer. BillThor BillThor 27k 3 3 gold badges 34 34 silver badges 69 69 bronze badges. Using hard, intr is good advice. However, note that NFS doubles the timeouts with each try. Try to not restart your NFS service so often ; — bjanssen.
Your answer is correct. I also found another simple solution. On the node that says stale NFS handler, just umount and remount the folder again. The root cause for problems of this type is usually that the rpc. Yes, even if you mount by IP address, the names must be resolvable, because the NFS lock protocol uses names internally.
Please see this answer of mine in another NFS question. Try this script I wrote:! Here is an update:! Birgit Ducarroz 13 4 4 bronze badges. Birgit Ducarroz Birgit Ducarroz 51 1 1 silver badge 2 2 bronze badges. Stale file handle error means that the NFS server holds an old version of the files in his export path. An NFS server restart can sometimes help. This is especially true for file locking. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 3 years, 9 months ago. Active 3 months ago. Viewed 85k times. Any other alternative to troubleshoot this?
As clarification: I can mount it in another machine. I cannot mount it in another mountpoint on the affected machine. Improve this question. Jaken Yes, it is accessible by someone else. In fact I can mount it in another machine. Try to add -v to mount -t command. Maybe addition info will be issued. Are you trying reboot your machine? Add a comment.
0コメント