All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: out-of-band dedup status?
Date: Thu, 08 Dec 2016 19:36:38 +0100	[thread overview]
Message-ID: <1481222198.6563.3.camel@scientia.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Hey.

I just wondered whether out-of-band/"offline" dedup is safe for general
use... https://btrfs.wiki.kernel.org/index.php/Status kinda implies so
(it tells about unspecified performance issues), but this seems again
already outdated (kernel 4.7)...
:-(

My intention was to use it with duperemove, but AFAIU, the kernel
itself will anyway do a byte-by-byte comparison before any
deduplication, so in principle it should be totally safe regardless of
the stability of the userland tool, right?
Especially I wouldn't want that "identity" is only assumed because of
some checksum identity (or collision ;) ).

Also, is there anything to take note of when this is used with
compression and snapshots?

What when I use it with incremental send/receive... i.e. I dedupe the
"master" and then send/receive this to another btrfs... will it work
(that is will the copy be also deduplicated, with no longer needed
extents properly being freed)... or at least not cause any corruptions?

Any other things in terms of possible issues, data corruption, etc.
that one should know when using deduplication?


Thanks :)

Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]

             reply	other threads:[~2016-12-08 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 18:36 Christoph Anton Mitterer [this message]
2016-12-08 20:15 ` out-of-band dedup status? Jeff Mahoney
2016-12-08 20:41   ` Chris Murphy
2016-12-08 22:27     ` Christoph Anton Mitterer
2016-12-08 23:31     ` Marc Joliet
2016-12-09  0:45       ` Chris Murphy
2016-12-09  2:26         ` Darrick J. Wong
2016-12-09  2:54           ` Chris Murphy
2016-12-09  8:25             ` Adam Borowski
2016-12-09 12:29             ` Austin S. Hemmelgarn
2016-12-09 18:16               ` Darrick J. Wong
2016-12-09 19:18                 ` Chris Murphy
2016-12-09  8:43   ` Adam Borowski

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=1481222198.6563.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 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.