Actually, I am thinking that the right fix is to remove the check and the "--no-nfs-version 3" item completely, because:
- There is no similar check for nfs versions 2 or 4, so it's weirdly inconsistent
- As bug 897644 shows, it won't be possible to fix it completely anyway
- We don't know why we need to pass that option to rpc.mountd in the first place!
If this was to prevent a crasher caused by a client bug, I don't believe a modern linux client will crash if it attempts to mount an nfsv3 mount if rpc.nfsd isn't serving version 3.
Actually, I am thinking that the right fix is to remove the check and the "--no-nfs-version 3" item completely, because:
- There is no similar check for nfs versions 2 or 4, so it's weirdly inconsistent
- As bug 897644 shows, it won't be possible to fix it completely anyway
- We don't know why we need to pass that option to rpc.mountd in the first place!
If this was to prevent a crasher caused by a client bug, I don't believe a modern linux client will crash if it attempts to mount an nfsv3 mount if rpc.nfsd isn't serving version 3.