Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1162122

Summary:	AFR gives EROFS when fop fails on all subvolumes when client-quorum is enabled
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.6.0	CC:	bugs, csuleski, cww, rabhat, storage-qa-internal, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-v3.6.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1157976
Clones:	1162150 (view as bug list)		Environment:
Last Closed:	2016-02-04 15:08:20 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:	1156224, 1157976
Bug Blocks:	1162150

Comment 1 Anand Avati 2014-11-10 10:38:19 UTC

REVIEW: http://review.gluster.org/9087 (cluster/afr: Preserve errno in case of failures on all subvols) posted (#1) for review on release-3.6 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2014-11-17 07:07:25 UTC

COMMIT: http://review.gluster.org/9087 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 6fbb140c293dcabaf6ec34315d7cc94de07c0782
Author: Pranith Kumar K <pkarampu>
Date:   Tue Oct 28 11:48:02 2014 +0530

    cluster/afr: Preserve errno in case of failures on all subvols
    
            Backport of http://review.gluster.org/8984
    
    Problem:
    When quorum is enabled and the fop fails on all the subvolumes,
    op_errno is set to EROFS which overrides the actual errno returned
    from bricks.
    
    Fix:
    Don't override the errno when fop fails on all subvols.
    
    Change-Id: I61e57bbf1a69407230ec172a983de18d1c624fd2
    BUG: 1162122
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/9087
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Kaushal 2016-02-04 15:08:20 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-v3.6.2, please open a new bug report.

glusterfs-v3.6.2 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/2015/01/glusterfs-3-6-2-ga-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user