Bug 762105 (GLUSTER-373) - Spawn fuse thread after a parent_up and wait and block until child_up
Summary: Spawn fuse thread after a parent_up and wait and block until child_up
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-373
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pavan Vilas Sondur
QA Contact:
URL:
Whiteboard:
: GLUSTER-220 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-11 14:23 UTC by Pavan Vilas Sondur
Modified: 2010-01-23 19:17 UTC (History)
3 users (show)

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

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

Description Pavan Vilas Sondur 2009-11-11 14:23:19 UTC 
The fuse process should be spawned immediately after a PARENT_UP and should block until a CHILD_UP is received. This will prevent a hang on an access on the mountpoint if a 'connect' hasn't been successful and times out. The fuse process will time out waiting for CHILD_UP in 1 second.
Comment 1 Anand Avati 2009-11-13 07:13:57 UTC 
PATCH: http://patches.gluster.com/patch/2182 in master (mount/fuse: Prevent a hang on the mount point if no server is up when the client is started.)
Comment 2 Anand Avati 2009-11-13 09:21:23 UTC 
PATCH: http://patches.gluster.com/patch/2181 in release-2.0 (mount/fuse: Prevent a hang on the mount point if no server is up when the client is started.)
Comment 3 Anand Avati 2010-01-23 04:19:28 UTC 
*** Bug 220 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.