From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs dedup - available or experimental? Or yet to be?
Date: Sun, 29 Mar 2015 19:54:07 +0200 [thread overview]
Message-ID: <1427651647.4878.3.camel@scientia.net> (raw)
In-Reply-To: <enflub-up7.ln1@hurikhan77.spdns.de>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
On Sun, 2015-03-29 at 16:44 +0200, Kai Krakow wrote:
> Yes, the chosen "default" is probably not the best for this kind of utility.
> But I suppose it follows the principle of least surprise. At least every
> utility I'm daily using (like find) follows this default route.
But the default with all these tools is that they operate on the file
hierarchy and per default don't care about filesystems at all - or at
least not in their original meaning.
dedup is IMHO however a more filesystem internal centric operation...
more like defragmentation ore tune2fs.
Cheers.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-03-29 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 23:10 btrfs dedup - available or experimental? Or yet to be? Martin
2015-03-23 23:22 ` Hugo Mills
2015-03-25 1:30 ` Rich Freeman
2015-03-27 0:07 ` Martin
2015-03-27 0:30 ` Rich Freeman
2015-03-29 11:43 ` Kai Krakow
2015-03-29 12:31 ` Rich Freeman
2015-03-29 14:44 ` Kai Krakow
2015-03-29 17:54 ` Christoph Anton Mitterer [this message]
2015-03-29 17:51 ` Christoph Anton Mitterer
2015-03-27 20:51 ` Mark Fasheh
2015-03-27 20:44 ` Mark Fasheh
2015-05-13 16:23 ` Learner Study
2015-05-13 21:08 ` 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=1427651647.4878.3.camel@scientia.net \
--to=calestyo@scientia.net \
--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).