Bug 772090
Summary: | NFS mount fails. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Woodhouse <dwmw2> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | bfields, jlayton, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-23 14:43:34 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
David Woodhouse
2012-01-05 22:33:27 UTC
[root@twosheds ~]# systemctl show nfs-server.service | grep rpc.nfsd ExecStart={ path=/usr/sbin/rpc.nfsd ; argv[]=/usr/sbin/rpc.nfsd $RPCNFSDARGS ${RPCNFSDCOUNT} ; ignore_errors=no ; start_time=[n/a] ; stop_time=[Thu, 05 Jan 2012 22:31:40 +0000] ; pid=11132 ; code=exited ; status=0 } ExecStop={ path=/usr/sbin/rpc.nfsd ; argv[]=/usr/sbin/rpc.nfsd 0 ; ignore_errors=no ; start_time=[n/a] ; stop_time=[Thu, 05 Jan 2012 22:31:40 +0000] ; pid=11122 ; code=exited ; status=0 } [root@twosheds ~]# grep RPCNFSD /etc/sysconfig/nfs #RPCNFSDARGS="-N 2 -N 3" RPCNFSDARGS="-N 4" #RPCNFSDCOUNT=8 I tried editing that file so that RPCNFSDCOUNT is set, and then restarting nfs-server.service. But still it appears the same. I lie; setting RPCNFSDCOUNT explicitly does fix it. Do we need to make the unit file cope? Something like ${RPCNFSDCOUNT:-8} would suffice if it were being interpreted by bash, but I don't think it is. Perhaps we should just set RPCNFSDCOUNT to 8 before invoking /etc/sysconfig/nfs? We also need to fix the client behaviour. (In reply to comment #2) > I lie; setting RPCNFSDCOUNT explicitly does fix it. Do we need to make the unit > file cope? Something like ${RPCNFSDCOUNT:-8} would suffice if it were being > interpreted by bash, but I don't think it is. Perhaps we should just set > RPCNFSDCOUNT to 8 before invoking /etc/sysconfig/nfs? The problem stems for when the systemd enabled nfs-utils is installed the original /etc/sysconfig/nfs is not overwritten. Instead a /etc/sysconfig/nfs.rpmnew is create where the RPCNFSDCOUNT variable is probably not set (as it is in the .rpmnew version). Now with the systemd world order the RPCNFSDCOUNT has to be set since there is no bash like thing to make sure its always set. Long term the answer is probably to have rpc.* daemons all read from one configuration file when there are no command line arguments, similar to what mount.nfs does. > > We also need to fix the client behaviour. Hanging on ECONNREFUSED is by design. The assumption is the server is on its way up... *** This bug has been marked as a duplicate of bug 757452 *** |