Adam Borowski

`-b`/`--bytes` is already there, which should be enough for scripts. As for forcing a larger unit, that'd be reasonable, but I'm quite out of tuits these days.

I can't reproduce: ``compsize /`` starts fine for me; only some time later failing once recursing to a filesystem like ``/proc`` or ``/dev`` (unless given ``-x``). I've messed recently with...

... I'm an idiot. Obviously, I do get the error message you say, it just takes a while — unless the cache is hot or one of special filesystems gets...

Actually, there are multiple schemes people can legitimately want: * recursing all in-depth, counting only btrfs * recursing but pruning immediately And: * same sub-volume (ie, same "filesystem", ie `st.st_dev`)...

uncompressed vs referenced won't do that. There are other effects beside dedupe that affect the difference: slack at the end of incompletely filled pages, partial pinned extents, etc. The latter...

Yeah, a neutral name that includes both reduction and increases would work. I just have problems with coming with one :/

"usage" and "uncompressed" are the sum of sizes of all extents pinned by the file — that 128MB/1GB extent counts as its full length if even a single byte is...

"Not reflinked" isn't that simple -- a file reflinked within the same subvolume (eg. `cp` does that by default nowadays) should be included. Then, *compsize* cares about extents not files,...

Thank you for your effort, but I'm going to decline this. * distributions provide this package on a timely basis * without packages, there's no easy way to uninstall *...

With current restrictions, I don't think it makes sense to make *compsize* a library. The most cumbersome part is requiring root. A library that's usable only by root-only programs is...