Well, if TCP is supported (and even is the default!) I think it should work. I see switching to UDP as a workaround that I was lucky to find. There is no sense in accepting that a provided feature (NFS4 over TCP) does not work reliably. It would be better remove it, so other people don't fall into this trap (now I'm a bit provocative, I know)! The best would be to keep this bug report open until more data can be gathered which might lead to a proper fix. A fortunate side effect of the present bug report is that it serves as documentation of a workaround for others that just need to get the thing to work. That's part of the reason I wrote a descriptive title. On a side note, I realize that there may be an underlying problem in the TCP implementation, but NFS4 should not block completely even in that case.
-- "nfs: server not responding, timed out", then nfs4 locks up https://bugs.launchpad.net/bugs/477711 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
