chrismurphy added a new comment to an issue you are following: `` > vgoyal > In short, putting rootfs on thin lv increases complexity of default setup and > difficult to recover if something is bad. (thin pool full). Lot of people > don't like the idea of doing over provisioning for rootfs. They better have > peach of mind with pre-allocated rootfs.
OK got it. Without over provisioning, rootfs on thin LV is the same risk as Docker devicemapper using a dm-thin pool; what unacceptably increases risk is overprovisioning rootfs which is necessarily what happens when using fstrim on it to recoup extents for a devicemapper based reversion. Fair enough. I have seen it explode spectacularly with total data loss of all LV's using the thin pool and repair tools being unable to repair it; not just the fs that was writing at the time the exhaustion happened. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/186 _______________________________________________ cloud mailing list -- [email protected] To unsubscribe send an email to [email protected]
