Bug 152340
Summary: | NFSv4 does not work as expected | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Tom <tomryan> | ||||
Component: | nfs-utils | Assignee: | Jeff Layton <jlayton> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Ben Levenson <benl> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.0 | CC: | jlayton, steved | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-08-29 14:49:18 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: | |||||||
Attachments: |
|
Description
Tom
2005-03-28 17:50:59 UTC
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. |