Dne 18.9.2017 v 21:07 Gionatan Danti napsal(a):
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.
We can possibly print WARNING message only with the 1st. thin LV which causes
overprovisioining of thin-pool.
As for 'read-only' snapshot - it really doesn't matter - the overprovisioned
pool can in the 'worst' case end in out-of-space condition (i.e. fully
rewritten origin)
Regards
Zdenek
_______________________________________________
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/
