Bug 505540 - statd: Hostname mismatch causing problems between RHEL and NetApp
Summary: statd: Hostname mismatch causing problems between RHEL and NetApp
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: nfs-utils
Version: 5.3
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-12 10:40 UTC by Sachin Prabhu
Modified: 2018-10-20 02:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-13 17:15:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sachin Prabhu 2009-06-12 10:40:50 UTC
A notify request sent by a client is being ignored by the server resulting in unclaimed file locks on the server. The client in this case is a RHEL and the NFS server a Netapp server. The problem appears to be caused by a mismatch in the hostnames used by lockd and by statd.

The hostname on the server is set to a short name(ex: test). This short name is used by lockd when setting the hostname from which the locks were requested. 

The /etc/hosts is setup in such a way that a FQDN(ex: test.example.com) is returned by gethostbyaddr(). This is used by statd on the client when notifying servers that the machine has rebooted.

This is causing a problem on their Netapp servers which expects the same hostname used to set the locks and in by statd. 

This is a request to have the statd and the lockd to use the same source for setting hostnames.


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