Bug 762017 (GLUSTER-285)

Summary:	"first up child" can change during a transaction
Product:	[Community] GlusterFS	Reporter:	Vikas Gorur <vikas>
Component:	replicate	Assignee:	Vikas Gorur <vikas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	mainline	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Vikas Gorur 2009-09-27 12:44:58 UTC

The "first up child" is computed by looking at priv->child_up, which can change state during a transaction if a server comes back up or goes down. This can cause problems.

Comment 1 Anand Avati 2009-09-28 23:36:11 UTC

PATCH: http://patches.gluster.com/patch/1498 in master (cluster/afr: dir-write: Fix inode number handling.)

Comment 2 Anand Avati 2009-09-28 23:36:15 UTC

PATCH: http://patches.gluster.com/patch/1499 in release-2.0 (cluster/afr: dir-write: Fix inode number handling.)

Comment 3 Anand Avati 2009-10-05 09:16:46 UTC

PATCH: http://patches.gluster.com/patch/1659 in master (cluster/afr: Initialize local->first_up_child in AFR_LOCAL_INIT.)

Comment 4 Anand Avati 2009-10-05 09:17:04 UTC

PATCH: http://patches.gluster.com/patch/1660 in release-2.0 (cluster/afr: Initialize local->first_up_child in AFR_LOCAL_INIT.)