From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Deduplication tools
Date: Thu, 13 Apr 2017 13:19:37 +0000 (UTC) [thread overview]
Message-ID: <pan$89623$186e96bf$35782bfe$60bde099@cox.net> (raw)
In-Reply-To: 37e02202-b9a9-3953-7bc8-92c4d1fd485f@rqc.ru
Marat Khalili posted on Thu, 13 Apr 2017 14:06:07 +0300 as excerpted:
> After reading this maillist for a while I became a bit more cautious
> about using various BTRFS features, so decided to ask just in case: is
> it safe to use out-of-band deduplication tools
> <https://btrfs.wiki.kernel.org/index.php/Deduplication>, and which of
> them are considered more stable/mainstream? Also, won't running these
> tools exacerbate often mentioned stability/performance problems with
> too-many-snapshots? Any first-hand experience is very welcome.
Dedupe works by reflinking, which is how snapshots work too, so yes,
it'll trigger the same general issues.
However, while snapshots will reflink /everything/ in the snapshot, one
could hope dedupe won't find /that/ many duplicates and thus won't reflink
at the scale that snapshotting does. Tho of course if it doesn't find
at least some reasonable number of duplicates, it's hardly worth the
trouble to run.
So I'd say it may be worth doing, but do be aware of the scale of dedupe
reflinking. What I'd do here is consider that and then count it as
roughly another snapshot or two, or whatever, depending on how much
dedupeing you actually get.
--
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
prev parent reply other threads:[~2017-04-13 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 11:06 Deduplication tools Marat Khalili
2017-04-13 11:40 ` Austin S. Hemmelgarn
2017-04-13 13:19 ` Duncan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$89623$186e96bf$35782bfe$60bde099@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).