On Mon, Aug 28, 2017 at 12:49:10PM +0530, shally verma wrote: > Am bit confused over here, is your description based on offline-dedupe > here Or its with inline deduplication? It doesn't matter _how_ you get to excessive reflinking, the resulting slowdown is the same. By the way, you can try "bees", it does nearline-dedupe which is for practical purposes as good as fully online, and unlike the latter, has no way to damage your data in case of bugs (mistaken userland dedupe can at most make the kernel pointlessly read and compare data). I haven't tried it myself, but what it does is dedupe using FILE_EXTENT_SAME asynchronously right after a write gets put into the page cache, which in most cases is quick enough to avoid writeout. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!? ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din ⠈⠳⣄⠀⠀⠀⠀ -- 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
