From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: out-of-band dedup status?
Date: Fri, 09 Dec 2016 00:31:58 +0100 [thread overview]
Message-ID: <59259055.MCA93YCoJj@thetick> (raw)
In-Reply-To: <CAJCQCtQYof6yjOOc9rf5MFL=Gb-uai7CZGgygsThv+w=Hz=LFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Thursday 08 December 2016 13:41:36 Chris Murphy wrote:
> Pretty sure it will not dedupe extents that are referenced in a read
> only subvolume.
I've used duperemove to de-duplicate files in read-only snapshots (of
different systems) on my backup drive, so unless you're referencing some
specific issue, I'm pretty sure you're wrong about that. Maybe you're
thinking of the occasionally mentioned old dedup kernel implementation?
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-12-08 23:32 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 [this message]
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=59259055.MCA93YCoJj@thetick \
--to=marcec@gmx.de \
--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.