All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: out-of-band dedup status?
Date: Fri, 9 Dec 2016 09:43:52 +0100	[thread overview]
Message-ID: <20161209084352.GB28652@angband.pl> (raw)
In-Reply-To: <539d7c1c-5041-fb99-0ec5-81291f9f6609@suse.com>

On Thu, Dec 08, 2016 at 03:15:38PM -0500, Jeff Mahoney wrote:
> On 12/8/16 1:36 PM, Christoph Anton Mitterer wrote:
> > 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)...
> 
> SUSE supports it in SLE12 using our 3.12 and 4.4 -based kernels.  There
> haven't been a lot of changes to the kernel component of it.  It's
> pretty simple: check to see if the ranges are identical between two
> files and then reflink between them.
> 
> > Any other things in terms of possible issues, data corruption, etc.
> > that one should know when using deduplication?
> 
> There shouldn't be.  We haven't had any bug reports at SUSE.

I use it on busy machines on ancient kernels (3.14, one 3.13) without any
hint of problems other than dedupe itself being slow.


Meow!
-- 
u-boot problems can be solved with the help of your old SCSI manuals, the
parts that deal with goat termination.  You need a black-handled knife, and
an appropriate set of candles (number and color matters).  Or was it a
silver-handled knife?  Crap, need to look that up.

      parent reply	other threads:[~2016-12-09  8:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 18:36 out-of-band dedup status? Christoph Anton Mitterer
2016-12-08 20:15 ` 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 [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=20161209084352.GB28652@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=calestyo@scientia.net \
    --cc=jeffm@suse.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 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.