Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1155027

Summary: Excessive logging in the self-heal daemon after a replace-brick
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 3.6.0CC: bugs, gluster-bugs, ndevos, nsathyan, ravishankar, rhs-bugs, storage-qa-internal, vagarwal, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.6.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1151303
: 1155073 (view as bug list) Environment:
Last Closed: 2014-11-10 15:14:21 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: 969353, 969355, 1151303    
Bug Blocks: 1155073    

Comment 1 Anand Avati 2014-10-21 09:38:09 UTC
REVIEW: http://review.gluster.org/8957 (logs: Do selective logging for errnos) posted (#1) for review on release-3.6 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2014-10-22 10:04:30 UTC
COMMIT: http://review.gluster.org/8957 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 4b078cc079f221bb801988f1b5fed173ad40f9d6
Author: Pranith Kumar K <pkarampu>
Date:   Fri Oct 10 09:51:28 2014 +0530

    logs: Do selective logging for errnos
    
            Backport of http://review.gluster.org/8918
                        http://review.gluster.org/8955
    
    Problem:
    Just after replace-brick the mount logs are filled with ENOENT/ESTALE
    warning logs because the file is yet to be self-healed now that the
    brick is new.
    
    Fix:
    Do conditional logging for the logs. ENOENT/ESTALE will be logged at
    lower log level. Only when debug logs are enabled, these logs will
    be written to the logfile.
    
    Change-Id: If203d09e2479e8c2415ebc14fb79d4fbb81dfc95
    BUG: 1155027
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/8957
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krutika Dhananjay <kdhananj>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-11-10 15:14:21 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users