You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0434abd
Browse filesBrowse the repository at this point in the historyBrowse files
fix(vm-guard): decide on the unsent backlog (vfs/queue), not the cache size
27.10.2026 12:24 the guard paused the first full backup at 116 GiB and never
resumed it: it read diskCache.bytesUsed, the whole cache on disk, which keeps
uploaded bands for reading until --vfs-cache-max-size and does not fall when
the upload catches up. At 12:37 the real backlog was 30 GiB (966 bands in
vfs/queue) with the cache still at 116.
The reading now also carries the sum of vfs/queue sizes; pause and resume use
it, and a missing queue answer counts as unknown (do nothing), never as zero.
vm-status shows both numbers. Regression test with the 27.10 values.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments