Hi everyone, DeeDee Park a écrit : > I've been running a test on 2TB glusterfs. I've filled almost 700GB > total, but one > brick got full (0 Bytes Available). I had an aluu.min-free-disk option > set to 6GB, so I expected > that the volume would not fill up and leave 6GB *Available*. The drive > is a 500GB drive > and after formatting ext3, shows 459GB. I see it says that 440GB is > used, but that 19GB > is not useful to me, so I assume that the 6GB option would have meant > that I would have > 6GB available for use. Did I have to specify 25GB min-free-disk to get > 6GB of Available space? > I'm not sure if this is a bug, or if I'm incorrectly using the feature. > As a general rule, I like > to keep at least 10% available for each disk before going critical, but > I don't have a feature > to specify % of HD total size. > As referred in a previous mail, it seems that alu.limits.min-free-disk option now takes a percentage as correct value. Maybe it would solve your issue. Regards, Sebastien.
