Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 31802

Summary: NFS Locking not working due to rpc.statd
Product: [Retired] Red Hat Linux Reporter: Steven McDowall <sjm>
Component: nfs-serverAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
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 21:27:35 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:
Attachments:
Description Flags
strace showing statd system calls (and failures) none

Description Steven McDowall 2001-03-14 21:26:20 UTC 
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 21:27:32 UTC 
Created attachment 12667 [details]
strace showing statd system calls (and failures)
Comment 2 Michael K. Johnson 2001-03-14 22:08:43 UTC 

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