Il 18-09-2017 20:55 David Teigland ha scritto:
It's definitely an irritation, and I described a configurable
alternative
here that has not yet been implemented:
https://bugzilla.redhat.com/show_bug.cgi?id=1465974
Is this the sort of topic where we should start making use of
https://github.com/lvmteam/lvm2/issues ?
Hi, the proposed solution on BZ entry seems somewhat too "invasive" to
me.
I think it generally is a good idea to warn the users about possibly
unexptected behavior (ie: full pool).
However, for the specific use-case of taking read-only snapshots,
something as simple as "--silencepoolsizewarn" flag (or similar
configuration variable) would do the trick without distrupting
legitimate warnings.
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
