From: "Jérôme Poulin" <jeromepoulin@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>,
james northrup <northrup.james@gmail.com>
Subject: Re: cross-subvolume cp --reflink
Date: Mon, 20 Aug 2012 14:08:55 -0400 [thread overview]
Message-ID: <CALJXSJphSSGaXjBhtrzNKk3-F_xw-PMzWLT3AW6CLDGGoAN_qA@mail.gmail.com> (raw)
In-Reply-To: <CAPkEcwgSZ8umbFeuZ-fQAFAprBubL58eFSf4TQ=Z13ks8i9DOQ@mail.gmail.com>
On Thu, Aug 16, 2012 at 5:41 PM, james northrup
<northrup.james@gmail.com> wrote:
>
> dunno if this thread is dead, but im inclined to patch in cp --reflink to "fdupes" prog.
> It currently does provide a poor-man's dedupe via md5sum and hardlink, or delete.
>
> all the better if the distro-kernels can backport cross-snapshot reflinks sooner than later.
>
I was also wondering if it is possible for a program like fdupes to
use BTRFS checksum to make searching for duplicates much faster as you
wouldn't need to calculate checksum if BTRFS own checksum was
mismatched between 2 groups of checksum blocks?
next prev parent reply other threads:[~2012-08-20 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 15:27 cross-subvolume cp --reflink Norbert Scheibner
2012-04-01 15:30 ` Konstantinos Skarlatos
2012-04-01 16:41 ` Norbert Scheibner
2012-04-01 16:45 ` Konstantinos Skarlatos
2012-04-01 17:07 ` Norbert Scheibner
2012-04-01 17:19 ` Konstantinos Skarlatos
2012-04-01 18:11 ` Norbert Scheibner
2012-04-01 19:42 ` Konstantinos Skarlatos
[not found] ` <4F788EE2.4010105@univie.ac.at>
2012-04-01 18:39 ` Norbert Scheibner
2012-04-01 19:27 ` Konstantinos Skarlatos
2012-04-02 8:29 ` David Sterba
2012-04-01 15:42 ` Jérôme Poulin
2012-04-28 23:53 ` Hubert Kario
2012-04-29 20:05 ` Norbert Scheibner
2012-08-17 4:20 ` james northrup
2012-08-17 5:20 ` Marc MERLIN
2012-08-19 5:08 ` Mitch Harder
2012-08-19 6:43 ` Marc MERLIN
[not found] ` <CAPkEcwgSZ8umbFeuZ-fQAFAprBubL58eFSf4TQ=Z13ks8i9DOQ@mail.gmail.com>
2012-08-20 18:08 ` Jérôme Poulin [this message]
2012-08-21 0:20 ` james northrup
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=CALJXSJphSSGaXjBhtrzNKk3-F_xw-PMzWLT3AW6CLDGGoAN_qA@mail.gmail.com \
--to=jeromepoulin@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=northrup.james@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).