Bug 761932 (GLUSTER-200) - wrong log level for setlk EAGAIN error
Summary: wrong log level for setlk EAGAIN error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-200
Product: GlusterFS
Classification: Community
Component: logging
Version: 2.0.5
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-10 22:38 UTC by Amar Tumballi
Modified: 2013-12-19 00:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.


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