Hi,

I am getting some very annoying problems with nfs. After a server reboot I cannot immediately mount the home directory on the client via nfs, because of stale nfs file handles. I have to wait for half a day, then I can mount it. After that, I am getting errors with stale nfs file handles on the client every few hours. Often it is the ~/.ssh directory that cannot be accessed, so I cannot log in as a user via ssh. Or boost reports an 'Invalid cross-device link' when moving files from one directory to another (files that have only been accessed by the client). These errors disappear when I unmount the home directory on the client, restart nfs on the server, and mount the home directory again, but they will come back a few hours later.

I suspect it may have something to do with the raid service. On the server, the home directory is mounted as a software raid, using the xfs file system. As is written elsewhere, it is important for nfs that the underlying file system supports proper inodes. But xfs should certainly qualify, and why should the raid cause a problem? I don't understand. If you have any idea what I am missing, please let me know.