From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Why do full balance and deduplication reduce available free space?
Date: Mon, 02 Oct 2017 12:29:17 +0200 [thread overview]
Message-ID: <569fb850091001ea7476100eae050c00@linuxsystems.it> (raw)
In-Reply-To: <e5bd0dc3-f7a5-7461-0630-6f755425009f@mendix.com>
Il 2017-10-02 12:16 Hans van Kranenburg ha scritto:
> On 10/02/2017 12:02 PM, Niccolò Belli wrote:
>> [...]
>>
>> Since I use lots of snapshots [...] I had to
>> create a systemd timer to perform a full balance and deduplication
>> each
>> night.
>
> Can you explain what's your reasoning behind this 'because X it needs
> Y'? I don't follow.
Available free space is important to me, so I want snapshots to be
deduplicated as well. Since I cannot deduplicate snapshots because they
are read-only, then the data must be already deduplicated before the
snapshots are taken. I do not consider the hourly snapshots because in a
day they will be gone anyway, but daily snapshots will stay there for
much longer so I want them to be deduplicated.
Niccolò
next prev parent reply other threads:[~2017-10-02 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 10:02 Why do full balance and deduplication reduce available free space? Niccolò Belli
2017-10-02 10:16 ` Hans van Kranenburg
2017-10-02 10:29 ` Niccolò Belli [this message]
2017-10-02 11:14 ` Paul Jones
2017-10-02 11:26 ` Is it really possible to dedupe read-only snapshots!? Niccolò Belli
2017-10-02 14:15 ` Why do full balance and deduplication reduce available free space? Niccolò Belli
2017-10-02 19:35 ` Kai Krakow
2017-10-02 20:19 ` Niccolò Belli
2017-10-09 17:38 ` Kai Krakow
2017-10-02 20:27 ` Goffredo Baroncelli
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=569fb850091001ea7476100eae050c00@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=hans.van.kranenburg@mendix.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 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).