Stale Nfs File Handle Puppy
Did you reboot the NFS server? Did you do some sort of bulk move, rename or deletion of files or directories on the server? Are the clients changing files that other clients are trying to access?The normal source of a 'stale NFS file handle' is files being removed on the server.
Especially if a directory is removed. The usual fix is unmounting and remounting the volume, or rebooting the client. With some NFS server implementations, rebooting the server can cause this error, too.It sounds like there's something else going on here than the usual causes and more detail might be needed.
Jeff Layton2013-07-01 12:00:30 UTCAlmost certainly a kernel problem and something I happen to be working on at the moment. Unmounting stale NFS mountpoints is problematic at the moment. What kernel are you running on the client here? Steps to Reproduce: 1.wait for NFS server to crash for some reason 2.get timeouts on server 3.try to umount -l or umount -fIn this situation is the server coming back up? A server reboot due to crash or other issue should not cause stale NFS filehandles. What sort of server is this? Jeff Layton2013-07-01 13:01:56 UTCWe actually take quite a bit of care when it comes to old servers.
That one is likely just broken though, since it appears to be changing filehandles on a reboot. This is a major no-no for any sort of NFS server. When that happens, there's little the client can do to recover.That said, there.is. a regression in current mainline kernels, but it doesn't really have anything to do with old vs. New NFS servers. The problem is that when we're failing the pathwalk when the root of a NFS filesystem goes stale. When the pathwalk fails, we can't unmount the filesystem.I have a patch in the works that should fix this the right way and will probably post it upstream in a day or two.
Until then, I'm afraid there's little you can do but reboot the box. Tom Horsley2013-07-01 14:03:56 UTCI don't know if the server would have changed filehandles on a reboot or not. Like I said, it was powered off the entire time I was trying to do the umount.Whenever I've had stale NFS filehandles before (which, in fact, seems to be the single most common NFS error), I've always been able to recover by doing a umount -l then a remount (when umount -l was working, that is).
Stale Nfs File Handle Puppy 2
If I can do that manually on the client, I don't know why the client couldn't do it all by itself, so I wouldn't say there is little the client can do to recover. Jeff Layton2013-07-01 14:13:56 UTCIt shouldn't matter if you power down the box for a year. When it comes back up, it should be serving the.same. filesystem that it was before. I notice you're using drbd here, so perhaps you're did something to the filesystem between shutting it down and restarting it?In any case, the client can't recover in this situation all by itself because doing a unmount/remount cycle turns this into an entirely different mount as far as the kernel is concerned.
1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit). Microsoft directx 9 graphics device with wddm driver for windows 10. 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor.
You're redoing the lookup of the root.When the filehandle for an inode changes, the filesystem has no way to know what the inode actually.is. anymore. The lookup of the root of the mount is.long. since done. We have a filehandle but not necessarily any name that we can attach to it anymore.So, while we can make it easier to unmount an NFS mount that has a stale root filehandle, we can't do anything to automatically work around servers that suddenly decide to start throwing ESTALE errors on the root of the mount.Initial patch posted here.