woke up to find this in dmesg .. [see attachment]
Created attachment 304380 [details] dmesg output
It appears to me that its ext3 locking up not the NFS server...
Steve, I'm not so sure, it looks to me like ext3_mark_inode_dirty is an old artifact on the stack. Nothing which would call this function is present in the backtrace, which looks mostly like an nfs stat... the backtraces look pretty overwhelmingly nfs-related to me...
Ok... thanks for taking a look... I'll take this back...
it's worth noting too that since I rebooted the NFS server, this hasn't happened again.
Do you remember of you were doing anything special or just normal everyday NFS stuff...
I believe I was sleeping at the time. This went nuts during the night (probably cron.daily kicked something off which touched the mount point, and then things went downhill from there when the server stopped responding for whatever reason).
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Have you seen this problem lately?
not for a long time, lets close it.