From c81cf5b6f0db1c5c85eb2aeda046c5f0e7194296 Mon Sep 17 00:00:00 2001 From: root Date: Sun, 13 Sep 2026 04:30:28 +0000 Subject: [PATCH] fix: disk-gc-threat-response - correct access methods for kagentz and docker-vm - kagentz (105): use ssh root@kagentz (hostname), NOT pct exec 105 (shows loop0 59G, not real 99G) - docker-vm (109): use ssh root@192.168.68.7 (correct QEMU VM access) - abiba (100): use ssh root@abiba (hostname) - syslog-api (116): use pct-run 116 (correct) Verified: kagentz: 99G 8.9G 86G 10% / docker-vm: 158G 17G 135G 11% / abiba: 59G 13G 44G 23% / syslog-api: 40G 13G 25G 34% / --- disk-gc-threat-response.prose.md | 1 + 1 file changed, 1 insertion(+) diff --git a/disk-gc-threat-response.prose.md b/disk-gc-threat-response.prose.md index 4824a2f..b374e59 100644 --- a/disk-gc-threat-response.prose.md +++ b/disk-gc-threat-response.prose.md @@ -357,3 +357,4 @@ one-off GPU builds. No automated post-migration cleanup was in place. > container has no `pct` binary. > > **KVM VM:** CT 109 (docker-vm) is a QEMU VM, not LXC — access via SSH .7. +> **NOTE:** For kagentz (CT 105), use `ssh root@kagentz` (hostname), NOT `pct exec 105` — `pct exec 105` shows loop0 (59G) while `ssh root@kagentz` shows the real filesystem (99G). For docker-vm (CT 109), use `ssh root@192.168.68.7`, not `pct exec`. -- 2.54.0