Bug 505773

Summary:	NFS mount fails, "incorrect mount option specified
Product:	[Fedora] Fedora	Reporter:	Daniel Roesen <dr>
Component:	nfs-utils	Assignee:	Steve Dickson <steved>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	11	CC:	steved
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-06-13 18:35:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Roesen 2009-06-13 16:55:20 UTC

[root@trinity ~]# mount -v -t nfs discworld:/scratch /scratch
mount.nfs: timeout set for Sat Jun 13 18:53:44 2009
mount.nfs: text-based options: 'addr=<$IPADDR>' (placeholder for sanitization)
mount.nfs: mount(2): Operation not supported
mount.nfs: an incorrect mount option was specified

So DNS resolution works fine, no fstab entry, plain simple NFS mount. Fresh Fedora 11 installation, all post-release updates installed.

Workaround: using busybox.

[root@trinity ~]# busybox mount -t nfs discworld:/scratch /scratch
[root@trinity ~]#

Something is broken with mount.nfs I guess.

kernel-PAE-2.6.29.4-167.fc11.i686
nfs-utils-1.1.5-6.fc11.i586

Comment 1 Daniel Roesen 2009-06-13 18:24:48 UTC

Possibly duplicate of 505018 - very old NFS server... I'm going to test the pending nfs-utils update and report back.

Comment 2 Daniel Roesen 2009-06-13 18:30:04 UTC

Confirmation: The "-o proto=udp" workaround works fine.

Comment 3 Daniel Roesen 2009-06-13 18:34:26 UTC

nfs-utils-1.2.0-3.fc11.i586.rpm does NOT fix the issue.

Comment 4 Daniel Roesen 2009-06-13 18:35:58 UTC

I'm going to re-open Bug #505018 so we have all things in one place and close this one off as DUPLICATE.

*** This bug has been marked as a duplicate of bug 505018 ***