Dale, Have you had any problems with posix-locks. Yesterday I could not complete a du -h with it in the server chain. There have been a lot of fixes since but none I saw dealt directly with posix-locks. Harris ----- Original Message ----- From: "Dale Dude" <dale@xxxxxxxxxxxxxxx> To: "gluster-devel" <gluster-devel@xxxxxxxxxx> Sent: Monday, July 2, 2007 5:32:38 PM (GMT-0500) America/New_York Subject: Re: glusterfs crash with mainline-2.5 patch 260 with dbench Reply to list. Sorry for the direct email Harris ;) Dale Dude wrote: > Im now just using the below. After taking out iocache on the client > there is no more crash. Thanks much for the ping, Harris. > > Server: posix, posix-locks, io-threads, server > Client: client, io-threads, RR unify, writebehind, readahead > > Dale > > Harris Landgarten wrote: >> Dale, >> >> I was only using unify, readahead and writebehind on the client. I have io-threads on the server >> >> Harris >> >> ----- Original Message ----- >> From: "Dale Dude" <dale@xxxxxxxxxxxxxxx> >> To: "gluster-devel" <gluster-devel@xxxxxxxxxx> >> Sent: Monday, July 2, 2007 5:18:40 PM (GMT-0500) America/New_York >> Subject: Re: glusterfs crash with mainline-2.5 patch 260 with dbench >> >> Removing performance/io-cache from glusterfs-client.vol solves this. Now >> only using writebehind. >> >> Dale >> >> Dale Dude wrote: >> >>> Ran again with 261 (which only seems to fix perms?) with same results. >>> Using ubuntu dapper (2.6.15-28-amd64-server) with fuse 2.6.5. >>> >>> I only have one dbench test file so I have no choice. >>> -rw-r--r-- 1 root root 26214401 2005-11-19 21:19 >>> /usr/share/dbench/client.txt >>> >>> >> >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxx >> http://lists.nongnu.org/mailman/listinfo/gluster-devel >> >> >> _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/gluster-devel
