From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Marat Khalili <mkh@rqc.ru>, linux-btrfs@vger.kernel.org
Subject: Re: Deduplication tools
Date: Thu, 13 Apr 2017 07:40:15 -0400 [thread overview]
Message-ID: <8f0fd545-a2f0-f966-67c4-436e2870baa9@gmail.com> (raw)
In-Reply-To: <37e02202-b9a9-3953-7bc8-92c4d1fd485f@rqc.ru>
On 2017-04-13 07:06, Marat Khalili wrote:
> 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.
As a general rule, as long as you're careful, you generally shouldn't
have many issues. duperemove is the tool I would suggest for just
generic deduplication on BTRFS, as I know the developer is still active
and generally does a good job of getting bugs fixed. It may well make
performance problems with large numbers of snapshots worse, but probably
not by as much as you think (unless you have huge amounts of duplicate
data). Keep in mind also that batch deduplication can take a very long
time to do.
As a general rule though, if you're storing data that's consistently
structured and organized, you may want to consider doing a custom tool
to make the process more efficient. Any generic deduplication tool is
generally going to be pretty slow on large amounts of data, but
depending on what the data is and how it's organized, it may be possible
to determine duplicate data more efficiently than the block hashing
method used by most deduplication tools.
next prev parent reply other threads:[~2017-04-13 11:40 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 [this message]
2017-04-13 13:19 ` Duncan
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=8f0fd545-a2f0-f966-67c4-436e2870baa9@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mkh@rqc.ru \
/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).