Bug 1115199

Summary:	Unable to get lock for uuid, Cluster lock not held
Product:	[Community] GlusterFS	Reporter:	Peter Auyeung <pauyeung>
Component:	glusterd	Assignee:	GlusterFS Bugs list <gluster-bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5.1	CC:	amukherj, bugs, gluster-bugs, mashengcheng, pkarampu
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-31 01:49:08 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:

Description Peter Auyeung 2014-07-01 20:52:49 UTC

Description of problem:
During NFS concurrent write, etc-glusterfs-glusterd.vol.log shows the following log entries:

.2014-07-01 20:40:06.564499] I [glusterd-handler.c:1169:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req
.2014-07-01 20:40:06.972202] I [glusterd-handler.c:1114:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req
.2014-07-01 20:41:01.757756] E [glusterd-utils.c:153:glusterd_lock] 0-management: Unable to get lock for uuid: 7c6ac836-9ee1-4d90-9093-364b31db9a3a, lock held by: 4a21155b-d64f-4f88-a05f-11fc8346f83f
.2014-07-01 20:41:01.757799] E [glusterd-op-sm.c:5730:glusterd_op_sm] 0-management: handler returned: -1
.2014-07-01 20:41:01.760343] E [glusterd-utils.c:186:glusterd_unlock] 0-management: Cluster lock not held!
.2014-07-01 20:41:01.760386] E [glusterd-op-sm.c:5730:glusterd_op_sm] 0-management: handler returned: -1
.2014-07-01 20:41:33.801686] E [glusterd-utils.c:153:glusterd_lock] 0-management: Unable to get lock for uuid: 7c6ac836-9ee1-4d90-9093-364b31db9a3a, lock held by: 4a21155b-d64f-4f88-a05f-11fc8346f83f
.2014-07-01 20:41:33.801718] E [glusterd-op-sm.c:5730:glusterd_op_sm] 0-management: handler returned: -1
.2014-07-01 20:41:33.803919] E [glusterd-utils.c:186:glusterd_unlock] 0-management: Cluster lock not held!
.2014-07-01 20:41:33.803958] E [glusterd-op-sm.c:5730:glusterd_op_sm] 0-management: handler returned: -1
.2014-07-01 20:45:07.973494] I [glusterd-handler.c:1169:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req
.2014-07-01 20:45:07.974679] I [glusterd-handler.c:1169:__glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req

md5sum on files looks alright.
Volume heal info shows 0 heal-failed nor split-brain.
Gluster peer all connected

Not sure if that's cosmetic or actual locking issue.

Version-Release number of selected component (if applicable):
3.5.1

How reproducible:


Steps to Reproduce:
1. Create Volume
2. Enable quota
3. Mount volume on NFS client
4. Start 100 rsync process from another filesystems.

Actual results:

Log entries as shown above

Expected results:

No locking error

Additional info:

Comment 1 Atin Mukherjee 2014-10-31 01:49:08 UTC

2014-07-01 20:41:01.757756] E [glusterd-utils.c:153:glusterd_lock] 0-management: Unable to get lock for uuid: 7c6ac836-9ee1-4d90-9093-364b31db9a3a, lock held by: 4a21155b-d64f-4f88-a05f-11fc8346f83f

This log indicates that another peer (uuid : 4a21155b-d64f-4f88-a05f-11fc8346f83f) had already taken the cluster lock for one of the ongoing transaction and the framework doesn't allow multiple transactions to go through. With an ongoing transaction this log is expected considering another transaction attempt has been made.

Closing this bug, please re-open if the explanation is not satisfactory.

Comment 2 mark 2014-12-09 08:13:58 UTC

I want to say that the memory will taken 20GB by glusterd when this problem happend ?

Comment 3 Niels de Vos 2015-05-26 12:33:44 UTC

This bug has been CLOSED, and there has not been a response to the requested NEEDINFO in more than 4 weeks. The NEEDINFO flag is now getting cleared so that our Bugzilla household is getting more in order.