Bug 31801
| Summary: | NFS File Locking not working due to rpc.statd | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Steven McDowall <sjm> |
| Component: | nfs-utils | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | ||
| 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: | 2001-03-14 22:08:43 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: | |||
*** Bug 31802 has been marked as a duplicate of this bug. *** The chroot(2) bug will be fixed in the next release. |
From Bugzilla Helper: User-Agent: Mozilla/4.75 [en] (Windows NT 5.0; U) rpc.statd appears very changed since 6.2 and now in affect does not monitor any other machines. This in turn causes lockd not to behave for remote locks, and thus NFS locking is toast. The problem is that extra (and may I opine worthless) security was thrown in rpc.statd to make it work somewhat like anon ftp. Specifically it now chroots(".") where "." is /var/lib/nfs/statd (from a prior chdir call) Well, needless to say hardly anything works after this. All calls to libraries, /etc/hosts, etc. fail horribly w/ ENOENT since these are no longer accessible. The man page does NOT reflect any of these changes btw. Reproducible: Always Steps to Reproduce: 1.install rh7.0 w/ NFS 2.mount a remote file system (example we use are our home dirs) 3.run "gnp" to see the lack of locking 4. or use strace to see the calls from rpc.statd Actual Results: Error messages from both rpc.lockd and rpc.statd in /var/log/messages THe old 6.2 rpc.statd appears to work fine. TO fix this I would suggest either: 1) remove the questionable chroot call -or- 2) at install time, set up a correct "anon ftp" type environment under /var/lib/nfs/statd (i.e. /etc w/ hosts? /lib /usr/lib etc)