Bug 762017 (GLUSTER-285) - "first up child" can change during a transaction
Summary: "first up child" can change during a transaction
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-285
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-27 12:44 UTC by Vikas Gorur
Modified: 2009-11-11 13:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.)
Note You need to log in before you can comment on or make changes to this bug.