Bug 122711
Summary: | NFS - Cannot mount | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kyrre Ness Sjøbæk <kyrsjo> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields, steved, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-12-07 06:27:20 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: |
Description
Kyrre Ness Sjøbæk
2004-05-07 11:24:02 UTC
Use the '-v' option on the mount command... It will show the RPC error (if any) that is being returned. This might be a duplicate of 12294. Is the original poster using autofs to mount /home, or is it an fstab mount? I am using fstab, and then using mount -a to mount the stuff. Pretty shure (at least 99%) that i am using the correct options in fstab - the line looks something like 172.26.101.48:/home /home nfs defaults 0 0 (at least it that what i think it should look like - but I am not on the site rigth now, and won't be until friday. I've asked someone who should be on site tomorow to take a look, but i do no know if it will be done.) in the original comment rpcinfo -p is only showing nfs (version 2, tcp/udp, port 2049). Is this truly the case or just a typo? If so does mount -o vers=2 work? no, it was no typo :D Works now, but why didn't it detect it automatically? Is this still an issue with more recent FC kernels and autofs rpms? this is an fstab mount. I still have to specify -o vers=2 when mounting manually. But something changed during the upgrade of nfs-utils earlier this week - suddenly stat() became *very* slow. I am going to open another bug at that one. how are things with the 2.6.9 based errata kernel ? The vers=2 stuff or the stat (that was LDAP... I don't know what was wrong, it migth have been the server... "Fixed" it by enabeling nscd.. But we are almost finished swithching out that old crap box with a new server - debian sarge - and it don't have any problems with nfs v3...) |