Bug 762105 (GLUSTER-373)

Summary:	Spawn fuse thread after a parent_up and wait and block until child_up
Product:	[Community] GlusterFS	Reporter:	Pavan Vilas Sondur <pavan>
Component:	core	Assignee:	Pavan Vilas Sondur <pavan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	mainline	CC:	aavati, gluster-bugs, krishna
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:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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. ***