OK. A feedback from NFS community indicates that, the reason why replacing /some-dir with /export/some-dir solved the problem was that, NFSv4 client failed to find the right path on NFS server, so it fell back to NFSv2.
However, in the reply from mail list(http://www.spinics.net/lists/linux- nfs/msg31326.html ), Bruce also mentioned an outdated part in this document. Following is the quoted text: > The advice to use "fsid=0" in the ubuntu howto is out of date. With a > recent server you should just export and mount /export/tigers as you > would with NFSv3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019938 Title: SettingUpNFSHowTo possible mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1019938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
