Bug 1012947 - nfs+afr+logging: "unlock failed on 1 unlock" seems meaningless
Summary: nfs+afr+logging: "unlock failed on 1 unlock" seems meaningless
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: pre-release
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Anuradha
QA Contact:
URL:
Whiteboard:
: 1012945 (view as bug list)
Depends On: 989362
Blocks: 1012945
TreeView+ depends on / blocked
 
Reported: 2013-09-27 12:31 UTC by Anuradha
Modified: 2016-09-20 02:00 UTC (History)
9 users (show)

Fixed In Version: glusterfs-3.5.0
Doc Type: Bug Fix
Doc Text:
Clone Of: 989362
Environment:
Last Closed: 2014-04-17 11:48:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Comment 1 Anand Avati 2013-09-27 12:38:05 UTC
REVIEW: http://review.gluster.org/6012 (Logging :  "unlock failed on 1 unlock" seems meaningless) posted (#2) for review on master by Anuradha Talur (atalur)

Comment 2 Anuradha 2013-09-27 12:41:45 UTC
*** Bug 1012945 has been marked as a duplicate of this bug. ***

Comment 3 Anand Avati 2013-09-30 06:55:34 UTC
REVIEW: http://review.gluster.org/6012 (Logging :  Improved the log message on unlock failure in afr_unlock_inodelk_cbk.) posted (#3) for review on master by Anuradha Talur (atalur)

Comment 4 Anand Avati 2013-09-30 19:55:03 UTC
COMMIT: http://review.gluster.org/6012 committed in master by Anand Avati (avati) 
------
commit 2526eea5dde0aa1af6ff43cf63f6e818798c8f2f
Author: Anuradha <atalur>
Date:   Fri Sep 27 17:42:17 2013 +0530

    Logging :  Improved the log message on unlock failure in afr_unlock_inodelk_cbk.
    
    "unlock failed on 1 unlock" seems meaningless in the log message. Improved it.
    
    Change-Id: If67d3f9d4aa5310d0b6728a6c89fa58a5cc93d12
    BUG: 1012947
    Signed-off-by: Anuradha <atalur>
    Reviewed-on: http://review.gluster.org/6012
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Gluster Build System <jenkins.com>

Comment 5 Niels de Vos 2014-04-17 11:48:57 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.5.0, please reopen this bug report.

glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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