On 23/05/2017 23:33, Eric Sandeen wrote:
Try setting EIO rather than ENOSPC. Even if you run out of space, xfs should not become corrupted. You may need to add space to successfully replay the log afterward, but if you do, it should replay and everyhthing should be consistent (which is not the same as "no data was lost") - is that not the case? As for xfs happily running with metadata errors, the tunable error behavior should make it stop more quickly, at least if you set it for EIO. It usually will eventually stop when it hits what it considers a critical metadata IO error... -Eric
Mmm ok, I need to play better with these tunables ;) Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx GPG public key ID: FF5F32A8 -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
