approx 141GB+143GB=283 avail to the cluster. see below.
Brick #1 (main gluster server)
matth at meathouse|11:01:56>
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
141G 15G 119G 12% /
Brick #2 (slave)
[root at localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
143G 143G 0 100% /
/dev/hda1 99M 13M 82M 13% /boot
tmpfs 470M 0 470M 0% /dev/shm
172.16.1.76:/gs-test 283G 158G 119G 58% /mnt/gluster
-matt
-------
Matt Hodson
Scientific Customer Support, Geospiza
(206) 633-4403, Ext. 111
http://www.geospiza.com
On Nov 9, 2010, at 10:57 AM, Luis E. Cerezo wrote:
> what's the size of the storage bricks?
>
>
> On Nov 9, 2010, at 12:46 PM, Matt Hodson wrote:
>
>> I should also note that on this non-production test rig the block
>> size on both bricks is 1KB (1024) so the theoretical file size
>> limit is 16GB. so how then did i get a file of 200GB?
>> -matt
>>
>> On Nov 9, 2010, at 10:34 AM, Matt Hodson wrote:
>>
>>> craig et al,
>>>
>>> I have a 2 brick distributed 283GB gluster cluster on CentoOS 5.
>>> we nfs mounted the cluster from a 3rd machine and wrote random
>>> junk to a file. i watched the file grow to 200GB on the cluster
>>> when it appeared to stop. however the machine writing to the file
>>> still lists the file as growing. it's now at over 320GB. what's
>>> going on?
>>>
>>> -matt
>>>
>>> -------
>>> Matt Hodson
>>> Scientific Customer Support, Geospiza
>>> (206) 633-4403, Ext. 111
>>> http://www.geospiza.com
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
> Luis E. Cerezo
>
> blog: http://www.luiscerezo.org
> fotofun: http://www.flickr.com/photos/luiscerezo/
> twitter: http://twitter.com/luiscerezo/
> Voice: +1 412 223 7396
>
