pub fn reclaimed_bytes(report: &MaintenanceReport) -> u64Expand description
The bytes gc_one took off the filesystem, as one number.
MaintenanceReport carries the before/after PAIR on purpose — a lone
“reclaimed” figure cannot tell a run that compacted from one that did
nothing — so this is the lossy projection the wire asks for and not the
shape the report should have had. A run that grew the store (an in-place
compaction that had to write before it could retire) reports 0 rather
than an underflowed u64.