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: Thu, 12 May 2016 15:56:20 +0200 [thread overview]
Message-ID: <60018ed4-023e-4ca6-8f74-e19b8849de65@linuxsystems.it> (raw)
In-Reply-To: <pan$331b6$43ad41cc$c9aa5858$e14154bc@cox.net>
Thanks for the detailed explanation, hopefully in the future someone will
be able to make defrag snapshot/reflink aware in a scalable manner.
I will not use use defrag anymore, but what do you suggest me to do to
reclaim the lost space? Get rid of my current snapshots or maybe simply
running bedup?
Niccolò
next prev parent reply other threads:[~2016-05-12 13:56 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 [this message]
2016-05-13 6:11 ` Duncan
2016-05-20 15:51 ` Niccolò Belli
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=60018ed4-023e-4ca6-8f74-e19b8849de65@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).