Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 97381 - mount reports "NFSv3 not supported" not always accurate
mount reports "NFSv3 not supported" not always accurate
Product: Red Hat Linux
Classification: Retired
Component: util-linux (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Elliot Lee
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-06-13 17:31 EDT by Arthur Dent
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-14 16:58:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Arthur Dent 2003-06-13 17:31:08 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When attempting to mount an NFS share to a mount point that doesn't exist, mount
seems to also report that "NFSv3 not supported!" even if it is.


[root@ts_10_1_30_172 /]# mount /corelog
NFSv3 not supported!
mount: mount point /corelog does not exist
[root@ts_10_1_30_172 /]# mkdir /corelog
[root@ts_10_1_30_172 /]# mount /corelog
[root@ts_10_1_30_172 /]# 

and the relevant /etc/fstab line: /corelog          nfs    
0 0

additional information:
I'm running a monolithic stock redhat kernel.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.attempt to mount an nfs share with nfsvers=3 to a non-existent mount point.

Actual Results:  mount will correctly indicate "mount: mount point /xxx does not
exist" but will also indicate "NFSv3 not supported!" even if NFSv3 is supported.

Expected Results:  mount should not incorrectly state that NFSv3 is not supported.

Additional info:
Comment 1 Elliot Lee 2003-07-14 16:58:12 EDT
Some obscure mount bug. Should be partly fixed in rawhide, but that makes the message 
go away in this situation only.

Note You need to log in before you can comment on or make changes to this bug.