Bug 452415
Summary: | NFS mounts fail because nfsd not mounted on /proc/fs/nfsd on server machine | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brian Morrison <bdm> |
Component: | module-init-tools | Assignee: | Jon Masters <jcm> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | dzheng, jcm, john.cooper |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-08-19 12:03:27 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
Brian Morrison
2008-06-22 14:40:47 UTC
This seems to have resolved itself now, possibly only caused by a failure to mount /proc/fs/nfsd on the one occasion during the upgrade. I'm going to mark it closed. <Sigh> Always happens when you do that. A further reboot of the nfs server has resulted in the /proc/fs/nfsd mount process failing silently. Will try to catch any error messages if this happens again. At present the command in /etc/modprobe.d/modprobe.conf.dist directs errors to /dev/null, but I'll change this temporarily. Did you get anything from the logging in the end? No, I have not seen the problem again, but having said that I don't reboot that often. I have a pending reboot after the most recent Fedora kernel update, if I don't see the problem again then I will mark this closed again. I suspect that this is some sort of odd race error that has now disappeared because a fair number of packages have been updated including various nfs related packages. No, not seen this happen again with new -108.fc9 kernel and several reboots due to power cuts, so I'm marking it closed. I've seen this same problem surface for the case of NFS support statically built into a kernel, when booting it in a userland installed with a kernel where NFS was compiled as a module. Bottom line is /proc/fs/nfsd isn't mounted on the server and mount attempts fail with: mount: <host>:<mountpoint> failed, reason given by server: Permission denied Supporting a kernel where NFS is statically linked may not be a goal of the installed userland, but given the amount of time required to isolate this failure it arguably should be. In this case the remedy lies in other than module-init-tools. I'm attaching it to this bug as I suspect a single solution will address both scenarios. Note I've seen this problem surface in both FC8 and FC9 installs. # mount localhost:/workspace /mnt/z mount: localhost:/workspace failed, reason given by server: Permission denied # echo $? 32 [failure as seen via 'strace -f rpc.mountd':] open("/proc/fs/nfsd/filehandle", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/proc/fs/nfs/filehandle", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or directory) # /bin/mount -t nfsd nfsd /proc/fs/nfsd # mount localhost:/workspace /mnt/z # echo $? 0 |