On 15/05/2017 17:33, Zdenek Kabelac wrote:> Ever tested this:
mount -o errors=remount-ro,data=journal ?
Yes, I tested it - same behavior: a full thinpool does *not* immediately put the filesystem in a read-only state, even when using sync/fsync and "errorwhenfull=y".
So, it seems EXT4 remounts in read-only mode only when *metadata* updates fail.
I prefer 'remount-ro' as the FS is still at least accessible/usable in some way.
Fair enought.
Things are getting better
Can you make an example?
So again - all has its price....
True ;) 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/
