Bug 1484722

Summary:	return ENOSYS for 'non readable' FOPs
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	arbiter	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.13.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1489511 (view as bug list)		Environment:
Last Closed:	2017-12-08 17:39:07 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:
Bug Blocks:	1489511

Description Niels de Vos 2017-08-24 08:28:05 UTC

Description of problem:
feedback at https://review.gluster.org/#/c/18103/1//COMMIT_MSG@15 :

AFR marks the arbiter brick as 'non readable', so any read-based FOP won't be sent on it.(See: http://review.gluster.org/13539). So I don't think this change is really needed. After 13539, even arbiter_readv() won't be hit as well.

It might be a good idea to have this defensive fix (unwind the FOP with failure) in the rogue case AFR does wind the read fop to arbiter.


Expected results:
No change in behaviour, AFR should not call the FOPs from the arbiter xlator in any case.

Comment 1 Worker Ant 2017-08-24 08:28:42 UTC

REVIEW: https://review.gluster.org/18103 (arbiter: return ENOTCONN for 'non readable' FOPs) posted (#2) for review on master by Niels de Vos (ndevos)

Comment 2 Worker Ant 2017-09-04 13:08:48 UTC

REVIEW: https://review.gluster.org/18103 (arbiter: return ENOTCONN for 'non readable' FOPs) posted (#3) for review on master by Ravishankar N (ravishankar)

Comment 3 Worker Ant 2017-09-05 06:00:22 UTC

REVIEW: https://review.gluster.org/18103 (arbiter: return ENOTCONN for 'non readable' FOPs) posted (#4) for review on master by Ravishankar N (ravishankar)

Comment 4 Worker Ant 2017-09-05 08:36:47 UTC

REVIEW: https://review.gluster.org/18103 (arbiter: return ENOSYS for 'non readable' FOPs) posted (#5) for review on master by Niels de Vos (ndevos)

Comment 5 Worker Ant 2017-09-05 14:03:43 UTC

COMMIT: https://review.gluster.org/18103 committed in master by Ravishankar N (ravishankar) 
------
commit b1352d0974328b367afa7360e9523585efb7178d
Author: Niels de Vos <ndevos>
Date:   Wed Aug 23 18:18:24 2017 +0200

    arbiter: return ENOSYS for 'non readable' FOPs
    
    AFR marks the arbiter as 'non readable'. This has been introduced with
    commit 8ab87137 (afr: do not set arbiter as a readable subvol in inode
    context). arbiter_readv() should not get called anymore, so it could be
    removed. However, it is a good defensive approach to have all the inode
    read FOPs that can not be handled by the arbiter to return ENOSYS.
    
    Change-Id: I6ea41680832859bd6790dc8d7440ee98d38205fc
    BUG: 1484722
    Signed-off-by: Niels de Vos <ndevos>
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: https://review.gluster.org/18103
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 6 Shyamsundar 2017-12-08 17:39:07 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.13.0, please open a new bug report.

glusterfs-3.13.0 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/announce/2017-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/