Hi Vikas. Sure thing, but let me first fill the cluster again, in order to see whether it really happens when the space ends. Also, can you tell me if it's normal for glusterfs client to take ~6.2% of physical memory (~4000MB) which translates to ~240MB? Maybe this because of caching as I have up to 512 caching defined? Here is the vol file again: [remote at ncserver ~]$ cat /etc/glusterfs/glusterfs.vol ## Reference volume "home1" from remote server volume home1 type protocol/client option transport-type tcp/client option remote-host 192.168.253.42 # IP address of remote host option remote-subvolume posix-locks-home1 # use home1 on remote host option transport-timeout 10 # value in seconds; it should be set relatively low end-volume ## Reference volume "home2" from remote server volume home2 type protocol/client option transport-type tcp/client option remote-host 192.168.253.41 # IP address of remote host option remote-subvolume posix-locks-home1 # use home1 on remote host option transport-timeout 10 # value in seconds; it should be set relatively low end-volume volume home type cluster/afr option metadata-self-heal on option favorite-child home1 subvolumes home1 home2 end-volume volume writebehind type performance/write-behind option aggregate-size 128KB option window-size 1MB subvolumes home end-volume volume cache type performance/io-cache option cache-size 512MB subvolumes writebehind end-volume Thanks. 2009/3/31 Vikas Gorur <vikas at zresearch.com> > Stas, > > Would it be possible to give us remote access to your cluster sometime > so that I can look at all the issues you are facing? > > Vikas > -- > Engineer - Z Research > http://gluster.com/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://zresearch.com/pipermail/gluster-users/attachments/20090331/9fc4f70a/attachment.htm>
