Bug 1425684

Summary:	Worker crashes with EINVAL errors
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Rochelle <rallan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, asrivast, avishwan, bugs, csaba, nbalacha, rallan, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-19	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1373373	Environment:
Last Closed:	2017-09-21 04:33:25 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:	1373373
Bug Blocks:	1417147

Description Kotresh HR 2017-02-22 05:46:20 UTC

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

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 2 Kotresh HR 2017-02-22 05:47:51 UTC

Upstream Patch:

https://review.gluster.org/#/c/15404/

Comment 5 Atin Mukherjee 2017-03-24 16:34:30 UTC

downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101413/

Comment 7 Rochelle 2017-08-11 06:02:33 UTC

Verified with build : glusterfs-geo-replication-3.8.4-39.el7rhgs.x86_64

No EINVAL crash errors were seen.

Moving this bug to verified.

Comment 9 errata-xmlrpc 2017-09-21 04:33:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774

Comment 10 errata-xmlrpc 2017-09-21 04:57:48 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774