Bug 1237174

Summary:	Incorrect state created in '/var/lib/nfs/statd'
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	common-ha	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	kkeithle, mzywusko, ndevos, nlevinki, rhs-bugs, sankarshan, skoduri, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1237165	Environment:
Last Closed:	2016-06-16 13:17:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1237165, 1238057

Description Soumya Koduri 2015-06-30 13:56:21 UTC

+++ This bug was initially created as a clone of Bug #1237165 +++

Description of problem:

NLM/NSM makes use of '/var/lib/nfs/statd' directory to store the lock related information, which will be used during lock reclaim.
In particular,
'/var/lib/nfs/statd/state' stores the NSM state number for any host using which client would detect server reboots.

But currently '/var/lib/nfs/statd/state' is created as directory instead of file due to a small bug. 

Without this fix, it will result in failures during lock reclaim and rpc.statd service restart.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2015-06-30 09:52:29 EDT ---

This bug is automatically being proposed for Red Hat Gluster Storage 3.1.0 by setting the release flag 'rhgs‑3.1.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 1 Anand Avati 2015-06-30 13:59:17 UTC

REVIEW: http://review.gluster.org/11468 (common-ha: Fix '/var/lib/nfs/statd/state' path creation) posted (#1) for review on master by soumya k (skoduri)

Comment 2 Niels de Vos 2016-06-16 13:17:51 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user