linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: mpe <michele@unipex.it>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Deduplication
Date: Mon, 26 Aug 2013 09:22:29 +0800	[thread overview]
Message-ID: <20130826012228.GA17457@localhost.localdomain> (raw)
In-Reply-To: <kv7c2j$3gf$1@ger.gmane.org>

On Fri, Aug 23, 2013 at 12:04:10PM +0200, mpe wrote:
> On 23/08/2013 09:42, Liu Bo wrote:
> >Hi,
> >
> >On Thu, Aug 22, 2013 at 09:28:09PM +0200, Florian Lindner wrote:
> >>Hello,
> >>
> >>some questions regarding btrfs deduplication.
> >>
> >>- What is the state of it? Is it "safe" to use?
> >>https://btrfs.wiki.kernel.org/index.php/Deduplication does not yield
> >>much information.
> >
> >For inband dedup, it's experimental because it introduces some format changes.
> >
> 
> In our tests we are trying btrfs for our internal storage backup
> backend and we like a lot compression! Now would like to test inband
> dedup.

dedup can cope with compression, too.

> Does those patchs (are v6 the last?) can be used on ubuntu lts? Do
> have a simple howt-to to follow?

I didn't try ubuntu lts yet, but the v6 patch set can be well applied on
3.11-rc4.

To enable dedup, you need to
1) mount DEV /PATH_OF_MNT -o dedup (or -o dedup_bs=xxxK)
2) btrfs dedup register /PATH_OF_MNT
3) write your data now :)


Feel free to tell me if any questions, thanks.

-liubo

      reply	other threads:[~2013-08-26  1:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 19:28 Deduplication Florian Lindner
2013-08-23  7:42 ` Deduplication Liu Bo
2013-08-23 10:04   ` Deduplication mpe
2013-08-26  1:22     ` Liu Bo [this message]

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=20130826012228.GA17457@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=michele@unipex.it \
    /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).