From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: <linux-btrfs@vger.kernel.org>
Cc: Duncan <1i5t5.duncan@cox.net>
Subject: Re: Amount of scrubbed data goes from 15.90GiB to 26.66GiB after defragment -r -v -clzo on a fs always mounted with compress=lzo
Date: Fri, 20 May 2016 17:51:15 +0200 [thread overview]
Message-ID: <dee51010-3b20-429f-806f-87a877d9001e@linuxsystems.it> (raw)
In-Reply-To: <pan$106d2$20dff0d0$cff8ba20$86e58020@cox.net>
On venerdì 13 maggio 2016 08:11:27 CEST, Duncan wrote:
> In theory the various btrfs dedup solutions out there should work as
> well, while letting you keep the snapshots (at least to the extent
> they're either writable snapshots so can be reflink modified
Unfortunately as you said dedup doesn't work with read-only snapshots (I
only use read-only snapshots with snapper) :(
Does dedup's dedup-syscall branch
(https://github.com/g2p/bedup/tree/wip/dedup-syscall) which uses the new
batch deduplication ioctl merged in Linux 3.12 fix this? Unfortunately
latest commit is from september :(
prev parent reply other threads:[~2016-05-20 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 19:50 Amount of scrubbed data goes from 15.90GiB to 26.66GiB after defragment -r -v -clzo on a fs always mounted with compress=lzo Niccolò Belli
2016-05-11 20:07 ` Christoph Anton Mitterer
2016-05-12 10:18 ` Duncan
2016-05-12 13:56 ` Niccolò Belli
2016-05-13 6:11 ` Duncan
2016-05-20 15:51 ` Niccolò Belli [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=dee51010-3b20-429f-806f-87a877d9001e@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=1i5t5.duncan@cox.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 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).