Bug 76198 - NFS locking fails to work?
NFS locking fails to work?
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Stephen Tweedie
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-17 22:03 EDT by Aleksey Nogin
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-21 15:32:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Aleksey Nogin 2002-10-17 22:03:07 EDT
Strace (client) shows:

fcntl64(3, F_SETLK, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = -1 ENOLCK
(No locks available)

dmesg (client) shows:

nsm_mon_unmon: rpc failed, status=-13
lockd: cannot monitor xxx.xxx.xxx.xxx
lockd: failed to monitor xxx.xxx.xxx.xxx

repeated many times (where xxx.xxx.xxx.xxx is the server's IP).

Client: Red Hat 8.0, 2.4.18-14smp
Server: Red Hat 7.2, fully updated (2.4.18-17.7.xsmp)
Comment 1 Stephen Tweedie 2002-10-21 08:35:40 EDT
First, could you please check your reverse DNS?  ie. on the client, do

  dig -x xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the server's IP).

If the DNS lookup fails, rpc.statd will refuse to monitor the requested host.
Comment 2 Aleksey Nogin 2002-10-21 13:18:03 EDT
Just checked, the reverse DNS is OK.
Comment 3 Stephen Tweedie 2002-10-21 15:32:26 EDT
Is it working in both directions (ie. server can resolve the client, too?)  Do
you have the "nfslock" service running on both client and server?  (Look for a
running process named "rpc.statd)
Comment 4 Aleksey Nogin 2002-10-21 19:16:56 EDT
Are, you are right - statd was not running on the client. And it's my fault - I
made too much read-only and it didn't have write access to /var/lib/nfs/statd. 
Sorry about that.

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