Hi Nathan, Just following up, do you see the problem with the latest code? Can you give us the DEBUG output? Thanks Krishna On 8/6/07, Krishna Srinivas <krishna@xxxxxxxxxxxxx> wrote: > Can you run glusterfs in the DEBUG mode and send the logs? > > glusterfs -f client.vol -L DEBUG -l /tmp/glusterfs.log /mnt/gluster > > can you glusterfs in DEBUG on vs0, kill the glusterfsd on vs1 and > mail the /tmp/glusterfs.log? > > Thanks > Krishna > > On 8/6/07, Nathan Allen Stratton <nathan@xxxxxxxxxxxx> wrote: > > On Mon, 6 Aug 2007, Krishna Srinivas wrote: > > > > > Hi Nathan, > > > > > > Can you confirm that you are not killing the server to which > > > the client connects? > > > > > > According to the spec, client connects to server on 127.0.0.1:6996 > > > Which server are you running here(vs0/vs1/vs2)? What is the ip address of the > > > server you are killing? > > > > So each server also has a client, so that is why I used loopback. So if I > > kill vs0 then server and client for vs0 are down. However clients on vs1 > > and vs2 also point to each localhost are still up. So they should still be > > working, but are locked. > > > > -Nathan > > > > > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@xxxxxxxxxx > > http://lists.nongnu.org/mailman/listinfo/gluster-devel > > >
