Our workaround so far is to force all clients to connect with nfs3 instead of nfs4 and to avoid doing major operations like file tree syncs over nfs, doing them on the nfsd host itself.
Either nfs3 doesn't get stuck and crash (case 1) or we're just lucky it hasn't returned yet, with minor mitigation by dropping load (case 2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315955 Title: nfsd hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1315955/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
