All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Florian Lindner <mailinglists@xgm.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Deduplication
Date: Fri, 23 Aug 2013 15:42:38 +0800	[thread overview]
Message-ID: <20130823074236.GA2229@localhost.localdomain> (raw)
In-Reply-To: <CAJtBfr-ZncC9iOB=GegDXhOsayEXVk6gfu2P2X8PeeOQk3hZ3Q@mail.gmail.com>

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.

> 
> - https://pypi.python.org/pypi/bedup says: "bedup looks for new and
> changed files, making sure that multiple copies of identical files
> share space on disk. It integrates deeply with btrfs so that scans are
> incremental and low-impact."
> 
> Is is file-based deduplcation only or is there also a block-based
> mode? Does not seem so according to the docs.

Both inband dedup and offband dedup patchset are floating on the list, and
inband is block-based, but I'm not sure about offband dedup.

-liubo

> 
> If so, what is the advantage to numerous other tools that replace
> duplicates by hard links? Performance?
> 
> Thanks,
> 
> Florian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-08-23  7:42 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 ` Liu Bo [this message]
2013-08-23 10:04   ` Deduplication mpe
2013-08-26  1:22     ` Deduplication Liu Bo

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=20130823074236.GA2229@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mailinglists@xgm.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.