In any case, I was told that the usual fix for this is to reboot. And that did it. I don't like that answer... it isn't an answer. It leaves a mystery behind. But it does allow people to mount that share again.
Oh, well problem gone :(
If anyone has any ideas as to what I could look at to further investigate the root cause of this issue next time it crops up, I'd appreciate it.
Pull out tcpdump (or better yet, wireshark) and snoop the NFS communications (if you use wioreshark, it will break it all down in a nice readable fashion - if you use tcpdump, you better learn how to decode NFS packets !). You'll then see whether it's the NFS server rejecting the write() or the kernel itself for some reason.
Then you'll have a better idea of where to look -- Michael O'Keefe | [EMAIL PROTECTED] Live on and Ride an 06 BMW R12GS HP2 | [EMAIL PROTECTED] / | I like less more or less less than |Work:+1 858 845 3514 / | more. UNIX-live it,love it,fork() it |Fax :+1 858 845 2652 /_p_| My views are MINE ALONE, blah, blah, |Home:+1 760 788 1296 \`O'| blah, yackety yack - don't come back |Fax :+1 858 _/_\|_, -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
