On Wed, Oct 14, 2015 at 1:09 AM, Zygo Blaxell <ce3g8...@umail.furryterror.org> wrote: > > I wouldn't try to use dedup on a kernel older than v4.1 because of these > fixes in 4.1 and later:
I would assume that these would be ported to the other longterm kernels like 3.18 at some point? > Do dedup a photo or video file collection. Don't dedup > a live database server on a filesystem with compression enabled...yet. LIkewise. Typically I just dedup the entire filesystem, so it sounds like we're not quite there yet. Would it make sense to put this on the wiki in the gotchas section? > Using dedup and defrag at the same time is still a bad idea. The features > work against each other You mentioned quite a bit about autodefrag. I was thinking more in terms of using explicit defrag, as was done by dedup in the past. It looks like duperemove doesn't actually do this, perhaps because it is also considered unsafe these days. Thanks, I was just trying to get a sense for where this was at. It sounds like we're getting to the point where it could be used in general, but for now it is probably best to run it manually on stuff that isn't too busy. -- Rich -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
