Open Forza-tng opened 1 year ago
There's, at present, no disk usage known for individual items. Measuring it would require calculating the set of extents referenced by the current item, rather that by all items processed. Doing so is of course not hard; cost: no extra I/O, double the current memory.
Outputting a single field needs only a trivial amount of tuits; it's just that my field of them is barren these days :/
From my point of view, it would be enough to show only the apparent size of the selected set, like how compsize works today.
When looking at the size of subvolumes and snapshots, I usually only want to look at the actual disk usage for the chosen set.
Example:
Instead of
Ultimately it would be nice to print a table for the chosen set, similar to what
btrfs fi du -s
does.