Il 14-04-2017 10:24 Zdenek Kabelac ha scritto:
But it's currently impossible to expect you will fill the thin-pool to full capacity and everything will continue to run smoothly - this is not going to happen.
Even with EXT4 and errors=remount-ro?
However there are many different solutions for different problems - and with current script execution - user may build his own solution - i.e. call 'dmsetup remove -f' for running thin volumes - so all instances get 'error' device when pool is above some threshold setting (just like old 'snapshot' invalidation worked) - this way user will just kill thin volume user task, but will still keep thin-pool usable for easy maintenance.
Interesting. However, the main problem with libvirt is that its pool/volume management fall apart when used on thin-pools. Basically, libvirt does not understand that a thinpool is a container for thin volumes (ie: https://www.redhat.com/archives/libvirt-users/2014-August/msg00010.html)
-- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: [email protected] - [email protected] GPG public key ID: FF5F32A8 _______________________________________________ linux-lvm mailing list [email protected] https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
