Bug 1277080

Summary:	quota: set quota version for files/directories
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	quota	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.6	CC:	bugs, byarlaga, gluster-bugs, smohan, storage-qa-internal, vagarwal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1272411	Environment:
Last Closed:	2015-11-17 06:01:43 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:	1265200, 1272411
Bug Blocks:	1275914

Comment 1 Vijay Bellur 2015-11-02 09:47:07 UTC

REVIEW: http://review.gluster.org/12487 (quota: add version to quota xattrs) posted (#1) for review on release-3.7 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Vijay Bellur 2015-11-03 05:03:49 UTC

COMMIT: http://review.gluster.org/12487 committed in release-3.7 by Raghavendra G (rgowdapp) 
------
commit 3d3176958b7da48dbacb1a5a0fedf26322a38297
Author: vmallika <vmallika>
Date:   Thu Oct 15 12:41:13 2015 +0530

    quota: add version to quota xattrs
    
    This is a backport of http://review.gluster.org/#/c/12386/
    
    When a quota is disable and the clean-up process terminated
    without completely cleaning-up the quota xattrs.
    Now when quota is enabled again, this can mess-up the accounting
    
    A version number is suffixed for all quota xattrs and this version
    number is specific to marker xaltor, i.e when quota xattrs are
    requested by quotad/client marker will remove the version suffix in the
    key before sending the response
    
    > Change-Id: I1ca2c11460645edba0f6b68db70d476d8d26e1eb
    > BUG: 1272411
    > Signed-off-by: vmallika <vmallika>
    > Reviewed-on: http://review.gluster.org/12386
    > Tested-by: NetBSD Build System <jenkins.org>
    > Reviewed-by: Krishnan Parthasarathi <kparthas>
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Manikandan Selvaganesh <mselvaga>
    > Reviewed-by: Raghavendra G <rgowdapp>
    
    Change-Id: I67b1b930b28411d76b2d476a4e5250c52aa495a0
    BUG: 1277080
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/12487
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: Raghavendra G <rgowdapp>

Comment 3 Raghavendra Talur 2015-11-17 06:01:43 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.7.6, please open a new bug report.

glusterfs-3.7.6 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://www.gluster.org/pipermail/gluster-users/2015-November/024359.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user