Hi, as I'm not sure if this file got to the right recipient, I'm posting it again. Regards, Patrick > Can you attach the complete client log file? > > regards, > > On Wed, May 13, 2009 at 10:11 PM, Patrick Ruckstuhl > <patrick@xxxxxxxxx > <mailto:patrick@xxxxxxxxx>> wrote: > > Hi, > > I had a disconnect in a DHT setup, there are two bricks that are at the > same time also clients > > After this, there seems to be something messed up as the mv operation > does not work anymore and reports "Can not move, file exists" > > > I'm using rc8 > > server.vol 1&2 > ### Log brick > volume log-posix > type storage/posix # POSIX FS translator > option directory /data/glusterfs/log # Export this directory > end-volume > > ### Add quota support > volume log-quota > type features/quota > option disk-usage-limit 100GB > subvolumes log-posix > end-volume > > ### Add lock support > volume log-locks > type features/locks > subvolumes log-quota > end-volume > > ### Add performance translator > volume log-brick > type performance/io-threads > option thread-count 8 > subvolumes log-locks > end-volume > > ### Add network serving capability to above brick. > volume server > type protocol/server > option transport-type tcp > option transport.socket.bind-address 192.168.0.4 > subvolumes log-brick > option auth.addr.log-brick.allow 192.168.0.2,192.168.0.3,192.168.0.4 # > Allow access to "brick" volume > end-volume > > > client.vol > ### Add client feature and attach to remote subvolume > volume log-remote-hip > type protocol/client > option transport-type tcp > option remote-host 192.168.0.3 # IP address of the remote brick > option remote-subvolume log-brick # name of the remote volume > end-volume > > ### Add client feature and attach to remote subvolume > volume log-remote-hop > type protocol/client > option transport-type tcp > option remote-host 192.168.0.4 # IP address of the remote brick > option remote-subvolume log-brick # name of the remote volume > end-volume > > > ### This is a distributed volume > volume log-distribute > type cluster/distribute > subvolumes log-remote-hip log-remote-hop > end-volume > > > > > Part of the client log file > 2009-05-09 16:33:19 N [client-protocol.c:6327:client_setvolume_cbk] > log-remote-hop: connection and handshake succeeded > 2009-05-10 06:25:03 E [fuse-bridge.c:1273:fuse_rename_cbk] > glusterfs-fuse: 979: /hop/apache2/access.log.49.gz -> > /hop/apache2/access.log.50.gz => -1 (File exists) > 2009-05-10 06:25:03 E [fuse-bridge.c:1273:fuse_rename_cbk] > glusterfs-fuse: 1111: /hop/apache2/error.log.16.gz -> > /hop/apache2/error.log.17.gz => -1 (File exists) > > > The server log file looks like it does not contain anything special > > Thanks for any ideas, > Patrick > > -- > -------------------------- > Origo - Code with the flow > http://origo.ethz.ch > Free collaboration and hosting for open and closed source projects > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > <mailto:Gluster-devel@xxxxxxxxxx> > http://lists.nongnu.org/mailman/listinfo/gluster-devel > > > > > -- > Raghavendra G > > > ------------------------------------------------------------------------ > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel -- -------------------------- Origo - Code with the flow http://origo.ethz.ch Free collaboration and hosting for open and closed source projects
Attachment:
client1.log.bz2
Description: Binary data
