@Andy Whitcroft, yes the nfs server in my situation (192.168.14.4) is the location from which the mounts are made by the workstation that locked up, sorry I should have specified that.
Whenever the nfs client running the lucid/maverick kernel locked up I first checked all the other nfs client workstations we have to ensure their mounts were working fine in addition to the nfs server (in fact my first step was to check our gigabit switches since I have had network equipment failures in the past that resulted in nearly the same kind of symptoms with locked up nfs clients, of course in those situations there were no kernel errors as we have seen here other than the usual "nfs: server X not responding, still trying", and simply replacing the switch with a spare fixed the problem in those instances). Another thing I forgot to mention previously is that we are using gigabit nics and switches along with jumbo frames on the lan (9k packet size). I am not sure if that has had some impact, yet I would be interested to find out if others have experienced this lockup with or without using jumbo frames on a gigabit lan. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
