Bug 31802 - NFS Locking not working due to rpc.statd
NFS Locking not working due to rpc.statd
Status: CLOSED DUPLICATE of bug 31801
Product: Red Hat Linux
Classification: Retired
Component: nfs-server (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 2001-03-14 16:26 EST by Steven McDowall
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-14 16:27:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
strace showing statd system calls (and failures) (27.63 KB, text/plain)
2001-03-14 16:27 EST, Steven McDowall
no flags Details

  None (edit)
Description Steven McDowall 2001-03-14 16:26:20 EST
rpc.statd is basically broken due to the new security "enhancements" added
in RH 7.0.  In effect, any lock requests to rpc.lockd fail because 
rpc.statd can't "monitor" anything.  This is due to rpc.statd not being
able to do just about anything after it starts (like accessng files).

The reason is that rpc.statd now chdirs to /var/lib/nfs/statd (which is
fine), then CHROOTS to "." !! Well, needless to say after the chroot
not much works since it can no longer access /etc, /usr/lib, etc.

I would suggest either removing the questionable "chroot" call or
making sure when installing that a full "anon ftp" sort of environment
exists under /var/lib/nfs/statd
Comment 1 Steven McDowall 2001-03-14 16:27:32 EST
Created attachment 12667 [details]
strace showing statd system calls (and failures)
Comment 2 Michael K. Johnson 2001-03-14 17:08:43 EST

*** This bug has been marked as a duplicate of 31801 ***

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