Bug 1217423

Summary:	glusterfsd crashed after directory was removed from the mount point, while self-heal and rebalance were running on the volume
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	core	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.6.3	CC:	bugs, rabhat, smohan, ssampat, vmallika
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v3.6.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1215550	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:	1215550
Bug Blocks:	1216965

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

REVIEW: http://review.gluster.org/10470 (quota: Validate NULL inode from the entries received in readdirp_cbk) posted (#1) for review on release-3.6 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2015-05-21 09:17:58 UTC

COMMIT: http://review.gluster.org/10470 committed in release-3.6 by Raghavendra Bhat (raghavendra) 
------
commit bfd7f71be79458f88777bc388d965e9c28b51435
Author: vmallika <vmallika>
Date:   Thu Apr 30 16:15:06 2015 +0530

    quota: Validate NULL inode from the entries received in readdirp_cbk
    
    This is a backport of http://review.gluster.org/#/c/10416/
    
    > In quota readdirp_cbk, inode ctx filled for the all entries
    > received.
    > In marker readdirp_cbk, files/directories are inspected for
    > dirty
    
    > There is no guarantee that entry->inode is populated.
    > If entry->inode is NULL, this needs to be treated as readdir
    >
    > Change-Id: Id2d17bb89e4770845ce1f13d73abc2b3c5826c06
    > BUG: 1215550
    > Signed-off-by: vmallika <vmallika>
    > Reviewed-on: http://review.gluster.org/10416
    > Tested-by: NetBSD Build System
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Raghavendra G <rgowdapp>
    > Tested-by: Raghavendra G <rgowdapp>
    
    Change-Id: Iace5a53efac58ab5a0a82bcfddfff6fb2a5b5068
    BUG: 1217423
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/10470
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    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