Il 24-05-2016 16:17 Zdenek Kabelac ha scritto:
Dmeventd should not talk to lvmetad at all - I'm saying this for
years....
There are some very very hard to fix (IMHO) design issues - and
locking lvmetad in memory would be just one of wrong (IMHO) ways
forward....
Anyway - let's see how it evolves here as there are further troubles
with lvmetad & dmeventd - see i.e. here:
https://bugzilla.redhat.com/show_bug.cgi?id=1339210
I'll follow it ;)
One more, somewhat related thing: when thin pool goes full, is a good
thing to remount an ext3/4 in readonly mode (error=remount-ro). But
what to do with XFS which, AFAIK, does not support a similar
readonly-on-error policy?
It is my understanding that upstream XFS has some improvements to
auto-shutdown in case of write errors. Did these improvements already
tickle to production kernels (eg: RHEL6 and 7)?
Any thoughts/suggestions on that?
Thanks.
--
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/
