Bug 710560

Summary: Cannot mount NFS exported from older linux server.
Product: Red Hat Enterprise Linux 6 Reporter: Alan <alan.cowles>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED INSUFFICIENT_DATA QA Contact: yanfu,wang <yanwang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-15 12:00:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alan 2011-06-03 17:34:36 UTC 
Description of problem:

After update to RHEL 6.1 and all associated package on Sunday May 29th, I have found that I cannot mount a specific NFS directory that I could before being exported from a Centos 5.5 box elsewhere. I have several other nfs mounts all being exported from Netapp filers, and they are working splendidly. When I attempt to mount, I get the following message:

mount.nfs: requested NFS version or transport protocol is not supported

I had seen a similar report of someone online using Fedora 11 and they found that it no longer supported mounting of NFS via UDP by default and you had to specify this in fstab. I did so but continue to get the same message.



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


How reproducible: Every time I mount from this other machine.


Steps to Reproduce:
1. mount /path/to/dir as specified in /etc/fstab
2.
3.
  
Actual results: Error message that the protocol or version is not supported.


Expected results: That it would mount correctly as it had on Sunday prior to OS update and reboot.


Additional info: Still investigating causes here as well as potential causes on exporting system, wanted to post bug to see if others had encountered similar issue.
Comment 2 Steve Dickson 2011-06-09 18:07:38 UTC 
Could you please post the following information

rpcinfo -p <server>

and then get a network trace of the problem with:

tshark -w /tmp/data.pcap host <server>
bzip2 /tmp/data.pcap
Comment 3 Steve Dickson 2011-08-11 18:15:09 UTC 
ping!