From: Rich Freeman <r-btrfs@thefreemanclan.net>
To: Kai Krakow <hurikhan77@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs dedup - available or experimental? Or yet to be?
Date: Sun, 29 Mar 2015 08:31:10 -0400 [thread overview]
Message-ID: <CAGfcS_nG3gt=copDrWS9TEmZ-dn6WD+HODU1SyxNVvbBqLXQ0A@mail.gmail.com> (raw)
In-Reply-To: <d35lub-tec.ln1@hurikhan77.spdns.de>
On Sun, Mar 29, 2015 at 7:43 AM, Kai Krakow <hurikhan77@gmail.com> wrote:
>
> With the planned performance improvements, I'm guessing the best way will
> become mounting the root subvolume (subvolid 0) and letting duperemove work
> on that as a whole - including crossing all fs boundaries.
>
Why cross filesystem boundaries by default? If you scan from the root
subvolume you're guanteed to traverse every file on the filesystem
(which is all that can be deduped) without crossing any filesystem
boundaries. Even if you have btrfs on non-btrfs on btrfs there must
be some other path that reaches the same files when scanning from
subvolid 0.
--
Rich
next prev parent reply other threads:[~2015-03-29 12:31 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 [this message]
2015-03-29 14:44 ` Kai Krakow
2015-03-29 17:54 ` Christoph Anton Mitterer
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='CAGfcS_nG3gt=copDrWS9TEmZ-dn6WD+HODU1SyxNVvbBqLXQ0A@mail.gmail.com' \
--to=r-btrfs@thefreemanclan.net \
--cc=hurikhan77@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).