mount.nfs fails stating incorrect mount option but succeeds if -v option is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
util-linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Trusty |
Confirmed
|
Undecided
|
Unassigned | ||
Utopic |
Won't Fix
|
Undecided
|
Unassigned | ||
Vivid |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mount
with /etc/fstab containing;
n2:/db /db nfs auto,nfsvers=3 0 0
OR containing
n2:/db /db nfs auto 0 0
# mount /db
fails with message "mount.nfs: an incorrect mount option was specified"
# mount n2:/db /db
also fails with the same message
BUT the following succeeds despite the "Operation not supported" message
# mount n2:/db /db -v
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 11 15:14:50 2010
mount.nfs: text-based options: 'addr=63.
mount.nfs: mount(2): Operation not supported
mount.nfs: trying 63.227.222.65 prog 100003 vers 3 prot UDP port 2049
mount.nfs: trying 63.227.222.65 prog 100005 vers 3 prot UDP port 32767
mount.nfs: text-based options (retry): 'addr=63.
n2:/db on /db type nfs (rw)
This system in question dual boots 10.04 and 8.04; under 8.04 ALL of the above succeeds without error messages.
This error is preventing NFS mounts in /etc/fstab; without a workaround or fix this prevents any deployment of Ubuntu 10.04 for us.
summary: |
- mount.nfs fails stating incorrect mount option but succeeds if -v or - with 8.04 + mount.nfs fails stating incorrect mount option but succeeds if -v option + is used |
Changed in util-linux (Ubuntu): | |
status: | New → Confirmed |
Changed in util-linux (Ubuntu): | |
status: | New → Incomplete |
tags: | added: rls-w-incoming |
Changed in util-linux (Ubuntu Utopic): | |
status: | New → Won't Fix |
Given the mounts did work if I used the -v option from the command line, I experimented with adding the options shown in the verbose output to the fstab options.
If I add the proto=udp option "an incorrect mount option" error message goes away and the mount succeeds as before.
n2:/db /db nfs auto,nfsvers= 3,proto= udp 0 0
I tried the other options, and the ordering of the options, and found adding proto=udp was the option that made the error go away.
As can be seen from the verbose output, in this instance I am trying to mount volumes on an older server that only supports NFS vers 3.