From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs dedup - available or experimental? Or yet to be?
Date: Fri, 27 Mar 2015 00:07:29 +0000 [thread overview]
Message-ID: <mf2701$d5k$1@ger.gmane.org> (raw)
In-Reply-To: <CAGfcS_=6iHH+4T6CH8ag6MSf2N5n37pE6USSOjDTv=BMmFHQaw@mail.gmail.com>
On 25/03/15 01:30, Rich Freeman wrote:
> On Mon, Mar 23, 2015 at 7:22 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
>> On Mon, Mar 23, 2015 at 11:10:46PM +0000, Martin wrote:
>>> As titled:
>>>
>>>
>>> Does btrfs have dedup (on raid1 multiple disks) that can be enabled?
>>
>> The current state of play is on the wiki:
>>
>> https://btrfs.wiki.kernel.org/index.php/Deduplication
>>
>
> I hadn't realized that bedup was deprecated.
>
> This seems unfortunate since it seemed to be a lot smarter about
> detecting what has and hasn't already been scanned, and it also
> supported defragmenting files while de-duplicating them.
>
> I'll give duperemove a shot. I just packaged it on Gentoo.
Excellent and very rapid packaging, thanks!
Already compiled, installed, and soon to be tried on a test subvolume...
Anyone with any comments on how well duperemove performs for TB-sized
volumes?
Does it work across subvolumes? (Presumably not...)
Thanks,
Martin
next prev parent reply other threads:[~2015-03-27 0:08 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 [this message]
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
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='mf2701$d5k$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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).