From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: Adam Borowski <kilobyte@angband.pl>, ce3g8jdj@umail.furryterror.org
Cc: Timofey Titovets <nefelim4ag@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: dduper - Offline btrfs deduplication tool
Date: Tue, 2 Oct 2018 21:35:15 +0530 [thread overview]
Message-ID: <20181002160515.GA28265@giis.co.in> (raw)
In-Reply-To: <20180907143107.gsixosfbswlqcbly@angband.pl>
Apologies for pretty delay in response. Thanks for the suggestions
and comments.
>On the other hand, full bit-to-bit comparison is faster and 100% safe
>With fideduperange the risk is more than minimized--it's completely
>eliminated.
Okay got it, will use fideduperange() as default option for the tool and
keep ficlonerange() as secondary option. Will make the code changes and
send a new patch soon. thanks!
Cheers.
Lakshmipathi.G
next prev parent reply other threads:[~2018-10-02 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 4:31 dduper - Offline btrfs deduplication tool Lakshmipathi.G
2018-09-05 16:00 ` Timofey Titovets
2018-09-07 3:57 ` Lakshmipathi.G
2018-09-07 14:31 ` Adam Borowski
2018-10-02 16:05 ` Lakshmipathi.G [this message]
2018-09-07 23:32 ` Zygo Blaxell
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=20181002160515.GA28265@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.com \
/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).