Bug 1373373

Summary:	Worker crashes with EINVAL errors
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1374626 1374627 1374628 1425684 (view as bug list)		Environment:
Last Closed:	2017-03-06 17:25:17 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:	1374626, 1374627, 1374628, 1425684

Description Aravinda VK 2016-09-06 06:39:31 UTC

Description of problem:
During Hybrid crawl if the files are unlinked then worker crashes with EINVAL error.

Steps to Reproduce:
1. Create Master Volume and generate data
2. Create Slave Volume and establish Geo-rep session and start(Starts with Hybrid Crawl for initial sync)
3. Once started wait for 2-5 seconds and delete files.

Actual results:
Worker crashes with EINVAL traceback

Expected results:
Workers should not crash

Comment 1 Worker Ant 2016-09-06 06:40:28 UTC

REVIEW: http://review.gluster.org/15404 (geo-rep: Fix ESTALE/EINVAL issue during set_{xtime,stime}) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Worker Ant 2016-09-08 16:15:45 UTC

COMMIT: http://review.gluster.org/15404 committed in master by Aravinda VK (avishwan) 
------
commit 9db2826cd8dbcc0fb58f5434c21d00ca5c15c491
Author: Aravinda VK <avishwan>
Date:   Tue Sep 6 12:02:02 2016 +0530

    geo-rep: Fix ESTALE/EINVAL issue during set_{xtime,stime}
    
    Setfattr may get ESTALE/EINVAL if a file is being unlinked.
    To prevent worker crashing, added retry for these error messages.
    
    On second retry it will get ENOENT and that error is handled by
    ignoring.
    
    BUG: 1373373
    Change-Id: Ic660fa13208366d57c8d3d492bbef611475e45b7
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/15404
    Reviewed-by: Saravanakumar Arumugam <sarumuga>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>
    Smoke: Gluster Build System <jenkins.org>

Comment 3 Shyamsundar 2017-03-06 17:25:17 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.10.0, please open a new bug report.

glusterfs-3.10.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/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/