From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: dduper - Offline btrfs deduplication tool
Date: Fri, 7 Sep 2018 09:27:28 +0530 [thread overview]
Message-ID: <20180907035728.GA7717@giis.co.in> (raw)
In-Reply-To: <CAGqmi74eMiHe7HK_oueaj0JZmy1Kp1NoOCrU0yheEE8MjngLKA@mail.gmail.com>
>
> One question:
> Why not ioctl_fideduperange?
> i.e. you kill most of benefits from that ioctl - atomicity.
>
I plan to add fideduperange as an option too. User can
choose between fideduperange and ficlonerange call.
If I'm not wrong, with fideduperange, kernel performs
comparsion check before dedupe. And it will increase
time to dedupe files.
I believe the risk involved with ficlonerange is minimized
by having a backup file(reflinked). We can revert to older
original file, if we encounter some problems.
>
> --
> Have a nice day,
> Timofey.
Cheers.
Lakshmipathi.G
next prev parent reply other threads:[~2018-09-07 8:37 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 [this message]
2018-09-07 14:31 ` Adam Borowski
2018-10-02 16:05 ` Lakshmipathi.G
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=20180907035728.GA7717@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--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).