On Thu, Aug 31, 2017 at 11:33:44AM +0100, Chris Cottam wrote: > > Yup, that's a problem, and it's going to be even more of a problem > > once people start using reflink to snapshot sparse VM images. I > > think that the extent rework is probably the most important thing we > > need to solve for COW to be generally usable. > > Assuming I was feeling brave, what should I be doing to limit the > chances of hitting this issue? Would smaller filesystems or lots of > memory on the host help etc? > Also what should I be monitoring to warn me before anything actually breaks? Make sure you have memory compaction enabled is the best bet, don't run under crazy memory pressure. I've not actually seen an actual deadlock due to it, just the possible memory allocation deadlock warnings from kmem_alloc (and lots of those). -- 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
