Disk caps and offline servers
Max disk (GB) blocks new uploads via catalog bytes; Off/unhealthy servers skip upload pick and can show Temporary offline.
Disk caps and offline servers
How capacity and status affect uploads and downloads.
Where to find it
Per-server edit forms (Max disk usage, Status). List columns On / Status. Fleet health via Run health checks or Admin → Health Center.
How it works
Max disk usage (GB) is a hard limit on *new* uploads when catalog used + new bytes would exceed the cap (upload can fail as full / 507). Cap uses catalog (DB) bytes (floor(GB * 1_000_000_000)), not a live df scan. Empty or 0 = unlimited; schema max 1,000,000 GB. New Local Server default is often 10 GB.
Upload selection skips servers that are not healthy, not On, trashed, disconnected remotes, over cap, or outside geo/targeting rules. No eligible server → 503 No storage server is available for upload.
Downloads work for On and Read-only. Off, missing, or trashed backends can show downloaders Temporary offline (button disabled; previews suppressed).
Common problems
Status On but uploads never land here
healthStatus is not ok - run health checks and fix connectivity / disk / credentials. Local over cap can report server_disk_quota_full.
Cap wrong vs disk free
Admin cap is catalog-based; clean trash/transfers if the DB thinks the server is full.