One more observation that I'll post here as *TENTATIVE*. All clients are , as I wrote earlier, 12.04 clients. The bug, as described above, occurs whenever one of the client's fstab entry uses the nfs filesystem:
192.168.1.2:/home /marcato/home nfs defaults,user,exec,hard,auto,nolock 0 0 However, the NFS server appears to act normally when all clients use nfs4: 192.168.1.2:/home /marcato/home nfs4 defaults,user,exec,hard,auto,nolock 0 0 Interesting, because the /etc/mtab of the corresponding client has vers=4 in the options, which those clients that use nfs4 don't have. So it appears that, after all, all clients use version 4, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322407 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
