The upper bound never moves, so there is no progress to track or persist.
There's no new on-disk state. There are no balance item updates during
-the balance unless the limit filter is used. A resume after an unmount or a crash needs nothing more than
-the balance item that is already there.
+the balance unless the limit filter is used. A resume after an unmount
+or a crash needs nothing more than the balance item that is already
+there.
On resume, the balance loop revisits only the chunks it left in place
above the point where it stopped (filtered out, ENOSPC, active swapfile)