Find the storage that is filling up
Which storage is nearly full?
Ask for every datastore over 80%, before a full disk stops your backups. Then read the usage yourself.
What you get: the one datastore you need to act on, named, with how full it is, before backups or VMs start failing.
Ask Quox
Section titled “Ask Quox”Ask in plain words:
Ask the Proxmox agent HYPERION: which Proxmox datastores are more than 80% full? Read only please.
▤ AOCL │ L1 identity complete · allowed · 2ms
▤ AOCL │ L3 policy gate complete · proceed · 4ms
◐ DELEGATE │ delegate_to_agent agent_id=atlas ✔ DELEGATE │ delegate_to_agent agent_id=atlas │ 1 tools used, 1 tool outcomes · 31.9s
⛓ AEE │ envelope opened · stream_success
Done, read-only. Here's the cluster storage picture, with the over-80% flag. Over 80% full Storage pbs-01 Node(s) shared (visible on hyp-01–hyp-07) Type pbs (backup) Used 1.70 TiB Total 1.79 TiB % Used 94.9% Only one datastore is over the threshold: the shared Proxmox Backup Server store pbs-01 , at about 94.9% full (source: proxmox_read). It shows up once per node in the listing because it's a shared backup target, so it's one physical store near capacity, not seven. Everything else (under 80%, for context) Storage │ Node │ Type │ Used │ Total │ % Used ──────────┼────────┼─────────┼──────────┼──────────┼─────── local-lvm │ hyp-02 │ lvmthin │ 622 GiB │ 976 GiB │ 63.7% local-lvm │ hyp-05 │ lvmthin │ 323 GiB │ 611 GiB │ 52.9% local-lvm │ hyp-03 │ lvmthin │ 1.84 TiB │ 3.52 TiB │ 52.2% local-lvm │ hyp-07 │ lvmthin │ 440 GiB │ 976 GiB │ 45.0% local-lvm │ hyp-04 │ lvmthin │ 1.06 TiB │ 2.43 TiB │ 43.8% hdd1t │ hyp-04 │ lvmthin │ 440 GiB │ 1.07 TiB │ 40.2% local │ hyp-01 │ dir │ 34 GiB │ 94 GiB │ 36.4% local │ hyp-02 │ dir │ 24 GiB │ 94 GiB │ 26.0% local │ hyp-04 │ dir │ 23 GiB │ 94 GiB │ 24.0% local-lvm │ hyp-01 │ lvmthin │ 195 GiB │ 976 GiB │ 20.0% local │ hyp-03 │ dir │ 19 GiB │ 94 GiB │ 20.0% local │ hyp-05 │ dir │ 16 GiB │ 94 GiB │ 16.9% local │ hyp-06 │ dir │ 15 GiB │ 94 GiB │ 16.5% local │ hyp-07 │ dir │ 7 GiB │ 94 GiB │ 7.8% local-lvm │ hyp-06 │ lvmthin │ 1.8 GiB │ 794 GiB │ 0.2% (source: proxmox_read, view=storage) Recommendation pbs-01 at 94.9% is the one to act on. It's the cluster's backup target, so if it fills, backups start failing silently. Worth pruning old backup groups or extending the datastore. I can pull the backup retention/prune picture with a backups read, or check PBS garbage-collection status, if you want me to dig in. No changes made here. Tools used: proxmox_read HYPERION found one datastore over 80%: the shared backup store pbs-01 , at 94.9% full (1.70 TiB of 1.79 TiB). Nothing was changed.
42.8s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 17 Oct 2026 · test report mvc4g1
HYPERION read the storage on every node and changed nothing. It flagged the one store over 80%, the shared backup store, and noticed that a shared store shows up once per node, so it is one store near capacity, not seven.
Do it yourself
Section titled “Do it yourself”quox vm storage{"success": true,"storages": [ { "storage": "pbs-01", "node": "hyp-06", "status": "available", "type": "pbs", "usedPercent": "94.9", "shared": 1, "content": "backup" },Look at usedPercent on each store. A store with shared set to 1 is one physical store that every node can see, so it appears once per node.
To see the CPU, memory and storage of one node:
quox vm node <node-name>What just happened
Section titled “What just happened”HYPERION read the storage list from your Proxmox cluster. Reading changes nothing, so no approval was needed. Freeing space, such as pruning old backups, is up to you.