<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.2">
<TITLE>Transport is not connected</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">When I a start a glusterfs client and kill it. An attempt to restart the glusterfs client process fails with the error below. It looks like the channel glusterfs uses to communicate with fuse is not released. If I use a different directory argument when I start a client glusters process it starts fine.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Is there a way to clean up resources so that a restart of client glusterfs wouldn't fail?</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">$ /usr/local/sbin/glusterfs -f ./client_test.vol -N -l /dev/stdout --log-level=DEBUG /tmp/local</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">2008-11-11 12:48:46 D [xlator.c:115:xlator_set_type] xlator: attempt to load file /usr/local/lib/glusterfs/1.3.12/xlator/mount/fuse.so</FONT></P>
<P><FONT SIZE=2 FACE="Arial">fuse: failed to access mountpoint /tmp/local: Transport endpoint is not connected</FONT>
<BR><FONT SIZE=2 FACE="Arial">2008-11-11 12:48:46 E [fuse-bridge.c:2699:init] glusterfs-fuse: fuse_mount failed (Transport endpoint is not connected)</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">2008-11-11 12:48:46 E [glusterfs.c:547:main] glusterfs: Initializing FUSE failed</FONT>
</P>
</BODY>
</HTML>