- Nfs readdirplus file handle is invalid stale update#
- Nfs readdirplus file handle is invalid stale tv#
- Nfs readdirplus file handle is invalid stale windows#
When NFS was designed these numbers referred to "inodes" in the mounted file system and the file system provides a nice fast way to convert an inode number to an actual "inode". A file handle is basically just a number, like 1, 2, 3. NFS relies on the notion of "file handles" to identify files on the server (AFP calls these "CNID's" but same concept). The problem with NFS (and also AFP) is that at it's core, it's an antiquated design. For example, any change to the Settings/Share settings page.Ĭ) This is the killer: with this option, it's possible to run out of memory Explanation follows.
Similar if the server is restarted.ī) Certain config changes on the server will have the same effect as above because they unmount/remount the user share file system. In this case you must unmount and remount on the client side. This should eliminate all stale file handle issues with these exceptions:Ī) If you Stop/Start the array with an active NFS mount by some client(s), then those clients will start seeing stale file handles. Save the attached file in the 'config' directory of your flash device and then Stop/Start the array (for the option contained there-in to take effect). I hate to say it, but adding "lookupcache=none,noac" to my mounts doesn't appear to improve matters at all. I don' know if this has been posted anywhere else, but I thought I would share my experiences. So far, I have been working this way for several days, and no "stale" incidents. Strangely enough, even on the "shares" that spanned multiple disk, I stopped getting the errors, even through I had NOT made any changes to their mounts. I stopped getting the stale handle messages at once (once they were unmounted/remounted). Under the new way, the fstab reads something like this:ġ0.0.1.10:/mnt/ disk4/Pictures /home/bkasten/Pictures nfs defaults,soft,nolock,nfsvers=3ĐĐįor the spanned shares I was going to switch to cifs if needed, but I wanted to get the non-span shares working first.
The fstab under the old way would read something like this:ġ0.0.1.10:/mnt/ user/Pictures /home/bkasten/Pictures nfs defaults,soft,nolock,nfsvers=3ĐĐ So I decided to make a change on how I would mount the non-span shares on my client computers. So, I read on the board that RC10 was better at this than RC11. I would have to umount/mount a dozen times a day, on every folder I was working in. I immediately began to get "stale nfs file handle" errors all the time.
Nfs readdirplus file handle is invalid stale tv#
TV = disk2, disk3, disk5, disk6, disk6,disk7, disk12 On this disk are several standard Linux folders (being used as mount points).
Nfs readdirplus file handle is invalid stale windows#
This was for every computer in the house, several Linux clients and 1 Windows client (Windows mounts using SMB). Using shares that were all focused on one (1) single disk (2TB). This is by far the largest amount of data, TV and Movies shares.Ģ. I have been using the "share" concept for mounts in two ways.ġ.
Nfs readdirplus file handle is invalid stale update#
I have had very little issues with stale handles.īut I needed to be able to use larger than 2TB drives, so that drove a need to update to a 5.0 xRC. I had been using unRAID 4.7 until recently with NFS for most of my client mounting.
0 kommentar(er)
