If /proc/mounts shows nvsvers=4 I would assume as well that nfsv4 is used. Formally I had the feeling that the examples looked like for really using nfsv4 one would need to have one entry in /etc/exports declaring a fsid=0 (iow the root) and then clients would ask for paths relative to that root. On one hand I *think* that I remember someone asking on irc and having issues when not following that. Which was another thing that seemed to have worked before.
For the debugging, I think it does give me a rough idea, just need to match that up against some code. Which will probably take a bit. But somehow it appears to try to connect but then to think the socket needs to be released for some reason. And possibly it either is failing to release it with some unexpected condition or incorrectly assumes it is still connected and repeats this forever. Cannot really think of a reason why this is related (or not) to another server running (at least yet). -- 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
