Bug 1248890

Summary:	AFR: Make [f]xattrop metadata transaction
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	replicate	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.3	CC:	bugs, gluster-bugs, kdhananj
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1248887	Environment:
Last Closed:	2015-10-14 10:30:28 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:	1248887
Bug Blocks:

Description Pranith Kumar K 2015-07-31 06:15:19 UTC

+++ This bug was initially created as a clone of Bug #1248887 +++

Description of problem:
(f)xattrop fops need to be made into transactions in order for these to work correctly when requested by translators that are above AFR in the client graph.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2015-07-31 02:06:01 EDT ---

REVIEW: http://review.gluster.org/11809 (cluster/afr: Make [f]xattrop metadata transaction) posted (#2) for review on master by Krutika Dhananjay (kdhananj)

--- Additional comment from Anand Avati on 2015-07-31 02:11:40 EDT ---

REVIEW: http://review.gluster.org/11809 (cluster/afr: Make [f]xattrop metadata transaction) posted (#3) for review on master by Krutika Dhananjay (kdhananj)

Comment 1 Anand Avati 2015-07-31 06:19:02 UTC

REVIEW: http://review.gluster.org/11810 (cluster/afr: Make [f]xattrop metadata transaction) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2015-09-01 05:56:56 UTC

COMMIT: http://review.gluster.org/11810 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 9f2a399055d3738457dbc461b1e9e99f718884e0
Author: Pranith Kumar K <pkarampu>
Date:   Sun Jul 26 11:19:28 2015 +0530

    cluster/afr: Make [f]xattrop metadata transaction
    
            Backport of http://review.gluster.com/11809
    
    Problem:
    When xlators above afr do [f]xattrop when one of the bricks is down, after the
    brick comes backup, the metadata is not healed because [f]xattrop is not
    considered a transaction.
    
    Fix:
    Treat [f]xattrop as transaction so that changes done by xlators above afr are
    marked for heal when some of the bricks were down at the time of [f]xattrop.
    
    BUG: 1248890
    Change-Id: Ibe69aa0ca6be9b4b4134dc2879b306e2e9c4cde8
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/11810
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Ravishankar N <ravishankar>

Comment 3 Pranith Kumar K 2015-10-14 10:30:28 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-glusterfs-3.7.5, please open a new bug report.

glusterfs-glusterfs-3.7.5 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-October/023968.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Pranith Kumar K 2015-10-14 10:38:51 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.5, please open a new bug report.

glusterfs-3.7.5 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-October/023968.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user