On Fri, May 18, 2018 at 13:10:02 -0400, Austin S. Hemmelgarn wrote: > Personally though, I think the biggest issue with what was done was not > the memory consumption, but the fact that there was no switch to turn it > on or off. Making defrag unconditionally snapshot aware removes one of > the easiest ways to forcibly unshare data without otherwise altering the The "defrag only not-snapshotted data" mode would be enough for many use cases and wouldn't require more RAM. One could run this before taking a snapshot and merge _at least_ the new data. And even with current approach it should be possible to interlace defragmentation with some kind of naive-deduplication; "naive" in the approach of comparing blocks only within the same in-subvolume paths. -- Tomasz Pala <gotar@xxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
