Bug 31801 - NFS File Locking not working due to rpc.statd
Summary: NFS File Locking not working due to rpc.statd
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact:
: 31802 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-14 21:14 UTC by Steven McDowall
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-14 22:08:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Steven McDowall 2001-03-14 21:14:39 UTC
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 

THe old 6.2 rpc.statd appears to work fine.

TO fix this I would suggest either:
1) remove the questionable chroot call 
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)

Comment 1 Michael K. Johnson 2001-03-14 22:08:39 UTC
*** Bug 31802 has been marked as a duplicate of this bug. ***

Comment 2 Bob Matthews 2001-03-14 22:16:39 UTC
The chroot(2) bug will be fixed in the next release.

Note You need to log in before you can comment on or make changes to this bug.