BG"mailto:dchepis...@superhosting.bg>>
Subject: [Gluster-users] cluster.min-free-disk
separate for each
brick
To: gluster-users@gluster.org
<mailto:gluster-users@gluster.org>
Subject: [Gluster-users] cluster.min-free-disk
separate for each
brick
To: gluster-users@gluster.org
<mailto:gluster-users@gluster.org>
Message-ID
sers-requ...@gluster.org> wrote:
Message: 1
Date: Sun, 14 Aug 2011 23:24:46 +0300
From: "Deyan Chepishev -
SuperHosting.BG"mailto:dchepis...@superhosting.bg>>
Subject: [Gluster-
>>
>>>>
>>>> On 15/08/11 20:00,
>>>> gluster-users-request@gluster.**orgwrote:
>>>>
>>>>> Message: 1
>>>>> Date: Sun, 14 Aug 2011 23:24:46 +0300
>>>>> From: "Deyan Chepishev -
>>>>> Supe
On 17/08/11 16:19, Dan Bretherton wrote:
Dan Bretherton wrote:
On 15/08/11 20:00, gluster-users-requ...@gluster.org wrote:
Message: 1
Date: Sun, 14 Aug 2011 23:24:46 +0300
From: "Deyan Chepishev - SuperHosting.BG"
Subject: [Gluster-users] cluster.min-free-disk separat
Hello,
Dan Bretherton wrote:
Dan Bretherton wrote:
On 15/08/11 20:00, gluster-users-requ...@gluster.org wrote:
Message: 1
Date: Sun, 14 Aug 2011 23:24:46 +0300
From: "Deyan Chepishev - SuperHosting.BG"
Subject: [Gluster-users] cluster.min-free-disk separate for each
Whit Blauvelt wrote:
Hi Deyan,
This may not be a useful suggestion, but why not just partition your storage
so that your bricks remain uniform?
==> Well this is a good suggestion unless you already have non uniform storage
with huge difference in brick sizes. The thing is that I was using one
Dan Bretherton wrote:
On 15/08/11 20:00, gluster-users-requ...@gluster.org wrote:
Message: 1
Date: Sun, 14 Aug 2011 23:24:46 +0300
From: "Deyan Chepishev - SuperHosting.BG"
Subject: [Gluster-users] cluster.min-free-disk separate for each
brick
To: gluster-users@gluster.org
Hi Deyan,
This may not be a useful suggestion, but why not just partition your storage
so that your bricks remain uniform? When you get more disk capacity because
you've got 3TB drives instead of 2TB in RAID5, so that you have 15TB rather
than 10TB per system, why not split the storage into 10TB a
wrote:
On 15/08/11 20:00, gluster-users-requ...@gluster.org wrote:
Message: 1
Date: Sun, 14 Aug 2011 23:24:46 +0300
From: "Deyan Chepishev - SuperHosting.BG"
Subject: [Gluster-users] cluster.min-free-disk separate for each
brick
To: gluster-users@gluster.org
Message-ID:<
On 15/08/11 20:00, gluster-users-requ...@gluster.org wrote:
Message: 1
Date: Sun, 14 Aug 2011 23:24:46 +0300
From: "Deyan Chepishev - SuperHosting.BG"
Subject: [Gluster-users] cluster.min-free-disk separate for each
brick
To: gluster-users@gluster.org
Message-ID:<
>
>
> My question is, is there a way to set cluster.min-free-disk per brick
> instead setting it for the entire volume or any other way to work around
> this problem ?
>
>
As of now, there are only two ways one can use 'min-free-disk'. It is either
with % (default is 10%), or with size, (in KB/MB/G
Hello,
I have a gluster set up with very different brick sizes.
brick1: 9T
brick2: 9T
brick3: 37T
with this configuration if I set the parameter cluster.min-free-disk to 10% it
applies to all bricks which is quite uncomfortable with these brick sizes,
because 10% for the small bricks are ~ 1T
13 matches
Mail list logo
