Red Hat Bugzilla – Bug 152340
NFSv4 does not work as expected
Last modified: 2014-06-18 03:34:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050322 Firefox/1.0.2 Red Hat/1.0.2-1.4.1
Description of problem:
I get repeated superblock errors when attempting to mount netapp exported filesystem via nfs4. Eventually, the connection will work (after multiple attempts over a prolonged time period)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot system, attempt nfs4 mount
2. keep trying and trying..
3. eventually it will work..
Actual Results: received superblock error
Expected Results: should mount (as it eventually does)
I will be uploading a strace output shortly.. I read there's an updated nfsutils out there somewhere.. will it be released for RHEL4 shortly?
Created attachment 112390 [details]
strace output of failed nfsv4 mount
I believe this is the problem....
mount("NFSSERVER:/vol/vol0/home/accounts/user", "/mnt/remote", "nfs4",
0xc0ed0000, 0x805c3e0) = -1 EINVAL (Invalid argument)
what are your arguments to the mount command and how are the
filesystems exported on the server?
Putting in NEEDINFO awaiting feedback requested in comment 2.
I thought I had posted an update yesterday.. odd..
regardless, i'm mounting a share exported on a netapp with kerberos 4 enabled.
I mount with the following command
mount -t nfs4 netapp:/export /mnt/point
sometimes it works, sometimes it doesn't.. it's not 100% failure, but when it
fails, I always get the superblock error..
Would it be possible to post a bzip2-ed
ethereal trace (i.e. tethereal -w /tmp/data.pcap)
of this failure?
FYI.. most of the time EINVAL errors translate to export issues.
No update to this bug in over 3 years. Closing with a resolution of INSUFFICIENT_DATA. Please reopen if this is still an issue.