<div dir="ltr">Hello, Niels<br><div class="gmail_quote"><div dir="ltr">On Tue, Apr 10, 2018 at 6:03 PM Sahina Bose <<a href="mailto:sabose@redhat.com">sabose@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 10, 2018 at 3:08 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In order to make thin-provisioning more stable in Gluster, I would like<br>
to see integrated monitoring of (thin) LVs and some form of acting on<br>
crucial events. One idea would be to make the Gluster Volume read-only<br>
when it detects that a brick is almost out-of-space. This is close to<br>
what local filesystems do when their block-device is having issues.<br>
<br></blockquote><div>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 - <a href="https://ovirt.org/develop/release-management/features/gluster/gluster-multiple-bricks-per-storage/" target="_blank">https://ovirt.org/develop/release-management/features/gluster/gluster-multiple-bricks-per-storage/</a>. Also, adding Denis, the feature owner.<br></div><div><br></div></div></div></div></blockquote><div><br></div><div><br></div><div>Sorry for the necroposting, but i would like to inform you, that monitoring of physically available (guaranteed) free space is implemented.</div></div></div>