#497: instance cap measures under the storage root; quota.enabled=false really disables #505
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-497"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #497.
maxTotalBytesnow measures bytes stored under the storage root via the same cached tree walk asperUserBytes(30s TTL), instead of the whole filesystem's statfs — on a shared volume the old check tripped always or never. Works on every backend, no Usager needed.Usage()) reports the same under-root figure when an instance cap is set;reserveByteskeeps its statfs free-space-floor meaning.storage.quota.enabledis now tri-state (*bool): explicitfalsekeeps the decorator out of the chain entirely (admin-set caps inert); absent keeps the always-installed behaviour (#178).TDD:
TestInstanceCapMeasuresUnderRoot,TestInstanceCapIgnoresSharedDiskUsage,TestInstanceCapUsageReportsUnderRootwitnessed red on the runner before the fix;TestMaxTotalBytesretired (superseded),TestCapacityGuardSkippedWithoutUsagerretargeted atReserveBytesonly; newTestQuotaEnabledTriState. Full suite green.