Bug 1241831 - quota: marker accounting can get miscalculated after upgrade to 3.7
Summary: quota: marker accounting can get miscalculated after upgrade to 3.7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: 3.7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard:
Depends On: 1241150 1241153
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-10 08:00 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:48 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.7.3
Clone Of: 1241153
Environment:
Last Closed: 2015-07-30 09:51:05 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2015-07-13 06:53:51 UTC
COMMIT: http://review.gluster.org/11614 committed in release-3.7 by Krishnan Parthasarathi (kparthas) 
------
commit 1509f6f2815cb75ecf45abef6d823c8cb30ed47b
Author: vmallika <vmallika>
Date:   Fri Jul 10 13:29:13 2015 +0530

    quota/marker: fix spurious failure afr-quota-xattr-mdata-heal.t
    
    This is a backport of http://review.gluster.org/#/c/11583
    
    During quota-update process if inode info is present in size-xattr and
    missing in contri-xattrs, then in function '_mq_get_metadata', we set
    contri-size as zero (on error -2, which means usage info present, but
    inode info missing).
    With this we are calculating wrong delta and updating the same.
    
    With this patch we are ignoring errors if inode info in xattrs are
    missing
    
    > Change-Id: I7940a0e299b8bb425b5b43746b1f13f775c7fb92
    > BUG: 1241153
    > Signed-off-by: vmallika <vmallika>
    
    Change-Id: Ie85fa84b5362ae179cc43402bd6a3a6d96a04b81
    BUG: 1241831
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/11614
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas>

Comment 2 Kaushal 2015-07-30 09:51:05 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.3, please open a new bug report.

glusterfs-3.7.3 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078
[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.