Now this also explains why I had a hard time (iow was not being able to) reproducing this here. Since this indeed is a rather unusual corner case, I can put it a little lower on the list. Still I would try to understand the debug output enough to have some better idea about how that windows app is getting NFS into such a mess. Maybe there is some way to at least weaken the effects.
About the fsid=0 exports. Yeah, it seems like a bit of a twisted way of setting things up. That face that I have to mount "<server>:/" for the export defined as fsid=0 I can grasp. But then how other mounts are matched to be below this and to be NFSv4 is not really that obvious. -- 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
