Dexter Filmore wrote:
Worth mentioning: fired up another box, same user/uid/groups/gid, can access that mount from there fine.
ahh ... sounds like you've hit one of the dreaded Linux NFS bugs. There are many.
So possibly a client issue on this Kub00ntu box.
It's more likely a problem on the *server*, and it has to do with attribute caching being broken. On heavily-accessed NFS filesystems, sometimes, without warning and for no apparent reason, these spurious permission denied errors will occur. When this happens, stop NFS services on the server and *all* clients, restart the server, restart the clients, and everything should be good to go. If not, the server will require a reboot because something in kernelspace has become corrupted (yay for having a kernelmode NFS daemon).
The bottom line is that Linux, although its NFS client implementation is fairly sound (albeit wack beyond imaginable sometimes), makes a horrible NFS server. If you want something to reliably serve NFS (and serve it properly), grab yourself a solaris box or a box running one of the myriad flavours of BSD.
Good luck, -Kelsey -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
