ops(nh3-dev): grow root into the 378 GB disk online; swap moved to /swapfile

Prime grew VM 102's scsi0 from 250 to 378 GB after the root alert hit 85%
twice in 14 h. The swap partition sat right after sda1 and blocked growth,
so the playbook moves swap to a 4 GB /swapfile, deletes sda5/sda2, grows
sda1 in place (start sector unchanged) and ext4 online, and sets initramfs
RESUME=none so boots don't wait for the vanished swap. Root is 372 GB, 58%.
This commit is contained in:
vh
2026-10-02 07:33:36 -07:00
parent 01c356e7fb
commit 6ec76bf35c
3 changed files with 112 additions and 0 deletions
+7
View File
@@ -10,6 +10,13 @@ Code sessions; **not** a Docker-stack host in the `stacks/` sense.
in auto-memory). Note: Claude Code sessions often run **natively on this box**, so
local Bash already executes here — no SSH-to-self needed for non-privileged work.
**Disk (2026-10-02):** VM 102 on nh3-pve, `scsi0` on `local-zfs`, **378 GB**, one partition (`sda1`, ext4,
372 GB). Swap is a **4 GB `/swapfile`**; there is no swap partition, and initramfs `RESUME=none`.
It was 250 GB with swap in `sda5` right after root, which blocked growth; the root alert hit 85%
twice in 14 h. To grow it again: resize `scsi0` in Proxmox, snapshot, then
`scripts/elway infra-ops@10.100.10.50 --playbook playbooks/nh3-dev-grow-root.yaml` (the swap and
partition steps skip themselves now; growpart + resize2fs do the work, online).
## What runs here
- **NH3 egress proxy — RETIRED 2026-09-06** (replaced by headscale exit nodes; `danted` disabled, config `.retired`). Was: durable internal-only SOCKS5 `socks5h://10.100.10.50:1080`