Bug 1335283 - Self Heal fails on a replica3 volume with 'disk quota exceeded'
Summary: Self Heal fails on a replica3 volume with 'disk quota exceeded'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: 3.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1332199 1332994
Blocks: 1311817 1335686
TreeView+ depends on / blocked
 
Reported: 2016-05-11 18:44 UTC by Pranith Kumar K
Modified: 2016-06-16 14:06 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of: 1332994
: 1335686 (view as bug list)
Environment:
Last Closed: 2016-06-16 14:06:02 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-05-11 18:53:41 UTC
REVIEW: http://review.gluster.org/14298 (cluster/afr: Do heals with shd pid) posted (#1) for review on release-3.8 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Vijay Bellur 2016-05-12 15:11:37 UTC
REVIEW: http://review.gluster.org/14309 (cluster/afr: Do heals with shd pid) posted (#1) for review on release-3.8 by Ravishankar N (ravishankar)

Comment 3 Vijay Bellur 2016-05-14 14:14:40 UTC
COMMIT: http://review.gluster.org/14298 committed in release-3.8 by Niels de Vos (ndevos) 
------
commit c2fce3fb987d5b795ed829c15e28d4b41177076e
Author: Pranith Kumar K <pkarampu>
Date:   Wed May 4 19:05:28 2016 +0530

    cluster/afr: Do heals with shd pid
    
    Multi-threaded healing doesn't create synctask with shd pid, this
    leads to healing problems when quota exceeds.
    
     >BUG: 1332994
     >Change-Id: I80f57c1923756f3298730b8820498127024e1209
     >Signed-off-by: Pranith Kumar K <pkarampu>
     >Reviewed-on: http://review.gluster.org/14211
     >Smoke: Gluster Build System <jenkins.com>
     >NetBSD-regression: NetBSD Build System <jenkins.org>
     >CentOS-regression: Gluster Build System <jenkins.com>
     >Reviewed-by: Ravishankar N <ravishankar>
    
    BUG: 1335283
    Change-Id: If59d8f88d8f4a3ca6a3b6e1c9dfd594dd93f542b
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/14298
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Ravishankar N <ravishankar>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

Comment 4 Niels de Vos 2016-06-16 14:06:02 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.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[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.