duperemove VS compsize

Very useful for identifying files that may need to get deduplicate or that can be removed entirely. Unfortunately, I don't think this will also find identical directories.

If deleting files isn't what you want, I'd suggest looking into deduplicating tools.

ZFS has its own de duplicator built in, which is nice. It should just deduplicate files and individual extents of files by itself once you enable it. Probably not a good idea on very write-heavy disks, but it's an option.

Other file systems with extent level deduplication can use https://github.com/markfasheh/duperemove to not only deduplicaye files, but also deduplicate individual extents. This can be very useful for file systems that store a lot of duplicate content, like different WINE prefixes. For filesystems without extent deduplication, duperemove should try hard linking files to make them take up practically no disks space.

ZFS now has reflink support, which doesn't require lots of RAM, but isn't done automatically while writing. You need to run something like https://github.com/markfasheh/duperemove

Then duperemove

Filesystems like Btrfs and XFS have support for deduplication, you can use a program like duperemove to save space.

Maybe you could use a file deduplication instead of a block based? https://github.com/markfasheh/duperemove

If not bees, do you run other programs for deduping? I see jdupes has support for BTRFS, https://github.com/jbruchon/jdupes, and also duperemove, https://github.com/markfasheh/duperemove.

It's a good filesystem, I use it with a special setup that needs a filesystem with snapshots. It's been stable for me, I run a duperemovehttps://github.com/markfasheh/duperemove) occasionally and that's about all the maintenance it needs.

With Btrfs or XFS you can easily deduplicate the data with tools like duperemove, potentially saving a lot of space if you've installed many small games.

The tool compsize can give you info about the compression state of your data. For example:

The obvious example is the Raid5/Raid6 implementation which is officially not recommended for current use; though that's not something I would use anyways. But I've also found that stuff like listing the compression ratio for volumes requires a separate program, unlike zfs where it's built-in.

If you want to diagnose where you think there may be space used up that you don't quite understand, then btrfs fi du and third party tools btdu and compsize are useful.

I'm going to add my N=1 anecdata if no one minds:

I've been running full Btrfs on my workstation since December 2021 with 0 issues (kernel 5.10). It survived multiple hard reboots and power offs, Ryzen 5000 CPUs seems to lose power every now and then on Linux (it's a known issue for years now that no one has figured out yet).

Having compression is great. compsize reports I've saved 33GB on my /home subvolume so far (https://github.com/kilobyte/compsize). I don't use snapshots, I just backup the whole thing.

Obviously this doesn't mean that in the future Btrfs won't eat my data, but so far it hasn't and I'm happy.

You can also use this tool to find out what the compression ratio of the data is ;).