That's only for deduplication.

I do like to deduplicate my BitTorrent downloads/seeding directory with my media directories so I can edit metadata to my heart's content while still seeding forever without having to incur 2x storage usage. I tune the `recordsize` to 1MiB so it has vastly fewer blocks to keep track of compared to the default 128K, at the cost of any modification wasting very slightly more space. Really not a big deal though when talking about multi-gibibyte media containers, multi-megapixel art embeds, etc.

▲

zenoprax 5 hours ago | parent | next [-]

Have you considered "reflinks"? Supported as of [OpenZFS 2.2](https://github.com/openzfs/zfs/pull/13392).

Haven't used them yet myself but seems like a nice use case for things like minor metadata changes to media files. The bulk of the file is shared and only the delta between the two are saved.

▲

yegle 7 hours ago | parent | prev [-]

cross-seed | cross-seed https://www.cross-seed.org/

	▲	bscphil 6 hours ago \| parent [-]
		I believe they are saying they literally edit the media files to add / change metadata. Cross-seeding is only possible if the files are kept the same.

▲

ekropotin 5 hours ago | parent | prev [-]

ZFS also uses RAM for read through cache aka ARC. However, I’m not sure how noticeable the effect from increased RAM would be - I assume it mostly benefit for read patterns with high data reuse, which is not that common.