I can also confirm this, with 2.36.4, 2.42 from quantal-updates (I couldn't go higher with 12.04.3 LTS's libc) and even with 2.36
This can completely fry netapp filers (i.e. clients with clientaddr=0.0.0.0 or others accessing the same filer) might have their transfer speed reduced to a few K (!) per sec or even stall with no I/O possible anymore at single processes. This is a major showstopper for all enterprise applications. Manually specified clientaddr mount options are a no-go for generically provisioned boxes (like cluster nodes, etc.) There's currently no solution to this here but dirty shell hackery in rc.local and friends... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
