Bug 847832 - kernel 3.6.0-0.rc1.git4.1.fc18 can't mount nfs (v4) mount
Summary: kernel 3.6.0-0.rc1.git4.1.fc18 can't mount nfs (v4) mount
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-13 17:11 UTC by Richard W.M. Jones
Modified: 2012-08-13 17:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-13 17:58:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2012-08-13 17:11:48 UTC
Description of problem:

With the F17 kernel, I was able to mount NFS (v4) mounts
just fine.  However while testing another bug I installed
the F18 kernel on this machine, and now NFS mounts no longer
work.

$ sudo mount -t nfs4 192.168.0.249:/mnt/media /mnt/media
mount.nfs4: No such device
$ sudo mount -t nfs 192.168.0.249:/mnt/media /mnt/media
mount.nfs: Connection timed out

Nothing significant in kernel messages ...

[18217.147943] FS-Cache: Loaded
[18217.149885] Key type dns_resolver registered
[18217.160996] FS-Cache: Netfs 'nfs' registered for caching

Also, I have another F18 machine which cannot mount the same
NFS partitions.

AFAIK nothing has changed on the server side (which is RHEL 6.3),
and other F16/F17 machines are able to mount the same partitions.

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

3.6.0-0.rc1.git4.1.fc18.x86_64

and on the other machine, 3.6.0-0.rc1.git3.2.bz844485.4.fc19.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Try mounting nfsv4 volume ...

Comment 1 Richard W.M. Jones 2012-08-13 17:13:50 UTC
Long thread here (still reading it ...)
http://www.spinics.net/lists/linux-nfs/index.html#31788

Comment 2 Richard W.M. Jones 2012-08-13 17:58:31 UTC
Cool, FIXED by updating to latest nfs-utils.


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