From: Jens Bauer <jens@gpio.dk>
To: linux-btrfs@vger.kernel.org
Subject: Re-using identical COW entries ?
Date: Fri, 3 Dec 2021 18:38:51 +0100 [thread overview]
Message-ID: <20211203183851411249.580fb47d@gpio.dk> (raw)
Hi.
Thinking about hashing and checksumming, I was wondering ...
Does BTRFS re-use identical COW entries ?
-Eg. if I'm compiling the same sources over and over, producing the same binaries over and over ...
Then the binaries would be deleted, then written again, deleted, ... repeat.
If deletion of unused entries would be just a bit that's set/cleared (which it's probably not, for safety), then
a COW entry could be re-used quickly (making writes faster).
It would of course require that the COW entry is not modified since last time (but if it was, it would have a different hash/checksum anyway).
Reason for thinking this way, is because I just copied 1.9 TB backup onto a disk-image which is on a BTRFS volume; the disk image uses 1.7TB space so far (and I'm incrementally updating that backup) and I know I have several identical files. Using a disk-image, because seen from Linux, it's a non-native file format.
Love
Jens
reply other threads:[~2021-12-03 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211203183851411249.580fb47d@gpio.dk \
--to=jens@gpio.dk \
--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