shally verma posted on Mon, 28 Aug 2017 12:49:10 +0530 as excerpted: > On Sat, Aug 26, 2017 at 9:45 PM, Adam Borowski <kilob...@angband.pl> > wrote: >> On Sat, Aug 26, 2017 at 01:36:35AM +0000, Duncan wrote: >>> The second has to do with btrfs scaling issues due to reflinking, >>> which of course is the operational mechanism for both snapshotting and >>> dedup. >>> Snapshotting of course reflinks the entire subvolume, so it's >>> reflinking on a /massive/ scale. While normal file operations aren't >>> affected much, >>> btrfs maintenance operations such as balance and check scale badly >>> enough with snapshotting (due to the reflinking) that keeping the >>> number of snapshots per subvolume under 250 or so is strongly >>> recommended, and keeping them to double-digits or even single-digits >>> is recommended if possible. >>> >>> Dedup works by reflinking as well, but its effect on btrfs maintenance >>> will be far more variable, depending of course on how effective the >>> deduping, and thus the reflinking, is. But considering that >>> snapshotting is effectively 100% effective deduping of the entire >>> subvolume (until the snapshot and active copy begin to diverge, at >>> least), that tends to be the worst case, so figuring a full two-copy >>> dedup as equivalent to one snapshot is a reasonable estimate of >>> effect. >>> If dedup only catches 10%, only once, than it would be 10% of a >>> snapshot's effect. If it's 10% but there's 10 duplicated instances, >>> that's the effect of a single snapshot. Assuming of course that the >>> dedup domain is the same as the subvolume that's being snapshotted. > > This looks to me a debate between using inline dedup Vs snapshotting or > more precisely, doing a dedupe via snapshots? > Did I understand it correct? if yes, does it mean people are still in > thoughts if current design and proposal to inline dedup is right way to > go for?
Not that I'm aware of and it wasn't my intent to leave that impression. What I'm saying is that btrfs uses the same underlying mechanism, reflinking, for both snapshotting and dedup. A rather limited but perhaps useful analogy from an /entirely/ different area might be that both single-person bicycles and full-size truck/ trailer rigs use the same underlying mechanism, wheels with tires turning against the ground, to move, while they have vastly different uses and neither one can replace the other. And just as the common to both cases tire has the limitation that it can be punctured and go flat, that applies to both due to the common mechanism used to move, so reflinking has certain limitations that apply to both snapshotting and dedup, due to the common mechanism used in the implementation. Of course taking the analogy much further than that will likely result in comically absurd conclusions, but hopefully when kept within its limits it's useful to convey my point, two technologies with very different usage at the surface level, taking advantage of a common implementation mechanism underneath. And because the underlying mechanism is the same, its limits become the limits of both overlying solutions, however they otherwise differ. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
