Bug 1294479

Summary:	quota: limit xattr not healed for a sub-directory on a newly added bricks
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	quota	Assignee:	Manikandan <mselvaga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, smohan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1294478
Clones:	1294608 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:52:41 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:	1294478
Bug Blocks:	1294608

Comment 1 Vijay Bellur 2015-12-28 12:07:24 UTC

REVIEW: http://review.gluster.org/13100 (quota: limit xattr for subdir not healed on newly added bricks) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Vijay Bellur 2015-12-29 16:28:17 UTC

COMMIT: http://review.gluster.org/13100 committed in master by Raghavendra G (rgowdapp) 
------
commit 72e736613169b778daa44e932443aaf2436432d9
Author: vmallika <vmallika>
Date:   Mon Dec 28 17:33:26 2015 +0530

    quota: limit xattr for subdir not healed on newly added bricks
    
    DHT after creating missing directory, tries to heal the
    xattrs. This xattrs operation fails as INTERNAL FOP key was not set
    
    Change-Id: I819d373cf7073da014143d9ada908228ddcd140c
    BUG: 1294479
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/13100
    Reviewed-by: Susant Palai <spalai>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: NetBSD Build System <jenkins.org>

Comment 5 Niels de Vos 2016-06-16 13:52:41 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