Bug 762733 (GLUSTER-1001)

Summary:	unclean termination upon getting signalled
Product:	[Community] GlusterFS	Reporter:	Csaba Henk <csaba>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	mainline	CC:	chrisw, fharshav, gluster-bugs, vijay
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 Csaba Henk 2010-06-13 14:50:47 UTC

Terminating glusterfs client with a signal leaves a stale fuse mount.

Prior to dynamic volume changes (79241696) cleanup_and_exit() recursed over the xlator graph calling their fini() methods. This is not happening now, therefore eg. fuse mount stays in place, defunct (other side effects might occur, this is just the one I observed).

Comment 1 Csaba Henk 2010-06-15 08:19:00 UTC


*** This bug has been marked as a duplicate of bug 971 ***

Comment 2 Anand Avati 2010-06-23 03:16:21 UTC

PATCH: http://patches.gluster.com/patch/3462 in master (io-threads: initialize conf->w_attr)

Comment 3 Csaba Henk 2010-06-23 03:31:58 UTC

Avati,

(In reply to comment #2)
> PATCH: http://patches.gluster.com/patch/3462 in master (io-threads: initialize
> conf->w_attr)

Did you maybe mistype the error number?

This bug has nothing to do with either of io-threads or Solaris, therefore I guess so...

Comment 4 Harshavardhana 2010-06-23 03:36:32 UTC

> 
> Did you maybe mistype the error number?
> 
> This bug has nothing to do with either of io-threads or Solaris, therefore I
> guess so...

this was regarding io-threads on server side solaris used to hang the server process.

Comment 5 Harshavardhana 2010-06-23 03:37:53 UTC

> this was regarding io-threads on server side solaris used to hang the server
> process.
 
Indeed the bug has no resemblance for the patch :)