[Gluster-devel] Monitoring and acting on LVM thin-pool consumption

Denis Chaplygin dchaplyg at redhat.com
Wed Jun 27 15:10:02 UTC 2018

Hello, Niels
On Tue, Apr 10, 2018 at 6:03 PM Sahina Bose <sabose at redhat.com> wrote:

> On Tue, Apr 10, 2018 at 3:08 PM, Niels de Vos <ndevos at redhat.com> wrote:
>> In order to make thin-provisioning more stable in Gluster, I would like
>> to see integrated monitoring of (thin) LVs and some form of acting on
>> crucial events. One idea would be to make the Gluster Volume read-only
>> when it detects that a brick is almost out-of-space. This is close to
>> what local filesystems do when their block-device is having issues.
>> For the oVirt-Gluster integration, where gluster volumes are managed and
> consumed as VM image store by oVirt - a feature was added to monitor and
> report guaranteed capacity for bricks as opposed to the reported size when
> created on thin-provisioned LVs/vdo devices. The feature page provide some
> details -
> https://ovirt.org/develop/release-management/features/gluster/gluster-multiple-bricks-per-storage/.
> Also, adding Denis, the feature owner.

Sorry for the necroposting, but i would like to inform you, that monitoring
of  physically available (guaranteed) free space is implemented.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20180627/19893133/attachment.html>

More information about the Gluster-devel mailing list