Bug 1217419

Summary:	DHT:Quota:- brick process crashed after deleting .glusterfs from backend
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	quota	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.3	CC:	bugs, mzywusko, nlevinki, nsathyan, rabhat, shmohan, smohan, storage-qa-internal, vagarwal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-v3.6.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1203629	Environment:
Last Closed:	2016-02-04 15:27: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:	1183988, 1203629, 1217432
Bug Blocks:	1216965

Comment 1 Anand Avati 2015-04-30 10:49:24 UTC

REVIEW: http://review.gluster.org/10469 (posix: handle failure from posix_resolve) posted (#1) for review on release-3.6 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2015-05-27 12:18:37 UTC

COMMIT: http://review.gluster.org/10469 committed in release-3.6 by Raghavendra Bhat (raghavendra) 
------
commit d0f62e8b4fc605c522f7971a82cbbf027e06960e
Author: vmallika <vmallika>
Date:   Thu Mar 19 07:02:24 2015 +0530

    posix: handle failure from posix_resolve
    
    This is backport of http://review.gluster.org/#/c/9941/
    
    > When building ancestory, posix_resolve gets the inode
    > from the gfid. We need to handle the failure case from
    > this function
    >
    > Change-Id: I19f0f0c739686b1b0ef96309212aa1c7911b3589
    > BUG: 1203629
    > Signed-off-by: vmallika <vmallika>
    > Reviewed-on: http://review.gluster.org/9941
    > Reviewed-by: Raghavendra Bhat <raghavendra>
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    > Tested-by: Pranith Kumar Karampuri <pkarampu>
    
    Change-Id: I9933b653e6bdf9fbfd1f65081622f47ed7f25e45
    BUG: 1217419
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/10469
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Bhat <raghavendra>

Comment 3 Kaushal 2016-02-04 15:27: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-v3.6.4, please open a new bug report.

glusterfs-v3.6.4 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] https://www.gluster.org/pipermail/gluster-users/2015-July/022826.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user