From: Eric Levy <ericlevy@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: de-duplicating +C files
Date: Wed, 7 Oct 2020 02:29:34 -0400 [thread overview]
Message-ID: <CA++hEgxkGhnbKBhwuwSAJn2BtZ+RAPuN+-ovkKLsUUfTRnD1_g@mail.gmail.com> (raw)
Recently a discussion [1] began about the desirability or risk of
applying a de-duplication operation on files with a C (no-CoW)
attribute set. The controversy rests largely on the observation that
calls to Btrfs currently fail for de-duplication between two files if
exactly one has the attribute set, but succeed in other cases, even in
which both have the attribute set. It may seem more natural that
success depends on neither file having the attribute set.
Comments would be welcome in either this thread, or perhaps even more
conveniently, in the Github discussion, over how this behavior of
Btrfs relates to the preferred operation of a de-duplication
application.
[1] https://github.com/markfasheh/duperemove/issues/251
next reply other threads:[~2020-10-07 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 6:29 Eric Levy [this message]
2020-10-07 10:07 ` de-duplicating +C files Adam Borowski
2020-10-07 10:12 ` Nikolay Borisov
2020-10-07 11:35 ` Eric Levy
2020-10-07 11:57 ` 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=CA++hEgxkGhnbKBhwuwSAJn2BtZ+RAPuN+-ovkKLsUUfTRnD1_g@mail.gmail.com \
--to=ericlevy@gmail.com \
--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).