Bug 761932 (GLUSTER-200)

Summary:	wrong log level for setlk EAGAIN error
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <amarts>
Component:	logging	Assignee:	Vikas Gorur <vikas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0.5	CC:	gluster-bugs, lakshmipathi, vraman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Amar Tumballi 2009-08-10 22:38:02 UTC

The following logs were logged in 'Warning' level, instead it should be in 'Debug' level. 

--------------
[2009-08-09 22:00:34] W [fuse-bridge.c:2278:fuse_setlk_cbk] glusterfs-fuse: 120376825: ERR => -1 (Resource temporarily unavailable)						
[2009-08-09 22:00:44] W [fuse-bridge.c:2278:fuse_setlk_cbk] glusterfs-fuse: 120376876: ERR => -1 (Resource temporarily unavailable)	
--------------

These logs are harmless for the process, as it says 'EAGAIN' to application, which happens in the case of other process having lock on the same file.

from the 'man 2 fcntl'
----
EAGAIN The operation is prohibited because the file has been memory-mapped by another process.
----

As these are harmless logs, this causes confusion to the administrators thinking GlusterFS may not be working properly, where as its working just fine, but logging in different log level.

Comment 1 Vikas Gorur 2009-09-03 09:39:21 UTC

http://patches.gluster.com/patch/1008/ (mount/fuse: Don't log setlk returning EAGAIN as a GF_LOG_ERROR) in mainline.

http://patches.gluster.com/patch/1007/ (features/locks: Set the right log level in a few places.) in mainline.