Bug 1410688

Summary:	[Mdcache] clients being served wrong information about a file, can lead to file inconsistency
Product:	[Community] GlusterFS	Reporter:	Poornima G <pgurusid>
Component:	disperse	Assignee:	Poornima G <pgurusid>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.9	CC:	amukherj, bugs, nchilaka, pkarampu, rcyriac, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1410375	Environment:
Last Closed:	2017-03-08 10:24:50 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:	1409808, 1410375
Bug Blocks:

Comment 1 Worker Ant 2017-01-06 05:42:15 UTC

REVIEW: http://review.gluster.org/16341 (ec: Invalidations in disperse volume should not update the stat) posted (#1) for review on release-3.9 by Poornima G (pgurusid)

Comment 2 Worker Ant 2017-01-17 14:55:50 UTC

COMMIT: http://review.gluster.org/16341 committed in release-3.9 by Pranith Kumar Karampuri (pkarampu) 
------
commit bec0532b9536d91629cb502eec2f48c443ac3b49
Author: Poornima G <pgurusid>
Date:   Thu Jan 5 15:36:02 2017 +0530

    ec: Invalidations in disperse volume should not update the stat
    
    Backport of http://review.gluster.org/16329
    
    Issue:
    In disperse volume, the file is present across bricks, hence the stat
    from one brick doesn't carry the valid size of the file. Therefore
    the upcall from one brick updating the md-cache results in wrong size
    being updated.
    
    Fix:
    If the notification is cache invalidation then, indicate md-cache that
    the attributes is invalid.
    
    >Reviewed-on: http://review.gluster.org/16329
    >Smoke: Gluster Build System <jenkins.org>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >Reviewed-by: Xavier Hernandez <xhernandez>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    (cherry picked from commit 95d07a3d2d68805d93d36a447436e27c48777939)
    
    BUG: 1410688
    Change-Id: Id89d2283478e70b62b435a8891fffc86d2be8cb2
    Signed-off-by: Poornima G <pgurusid>
    Reviewed-on: http://review.gluster.org/16341
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

Comment 3 Kaushal 2017-03-08 10:24:50 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.9.1, please open a new bug report.

glusterfs-3.9.1 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://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html
[2] https://www.gluster.org/pipermail/gluster-users/