testsAndMisc/docs/superpowers/contracts/tmp-space-2026-11-22.json
Krzysztof kuhy Rudnicki 70189149b2
Some checks are pending
md-naming / markdown naming convention (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (mypy, mypy) (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (pylint, pylint) (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (rest, ) (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (shellcheck, shellcheck) (push) Waiting to run
Python tests / test (push) Waiting to run
repo-contract / repo contract (push) Waiting to run
Shell tests / shell-tests (push) Waiting to run
Shell tests / lib-tests (push) Waiting to run
Shell tests / arch-tests (push) Waiting to run
Add fix_tmp_space.sh: 30G /tmp, /var/disktmp
/tmp is the stock tmp.mount tmpfs (size=50%, usrquota) and systemd caps
each user at 80% of it at login; a heavy build hit that cap with EDQUOT.

fix_tmp_space.sh writes a tmp.mount drop-in with the stock options and
size=30G, reloads systemd once and remounts /tmp live (never an unmount:
the X11 sockets live there). tmp_quota.py raises each logged-in user's
cap live to 80% of 30G through quotactl_fd, since systemd sets it only
at login. A sparse 64G ext4 image is loop-mounted at /var/disktmp (1777)
through one fstab line; tmpfiles.d empties it at boot and ages it 10d.

The fstab line adds x-systemd.before=systemd-tmpfiles-setup.service:
nofail drops the ordering, and in vmbox tmpfiles started 22 ms before
the mount finished, so the boot-time emptying could miss the image.

Failure paths:
- /tmp not a tmpfs: fail-closed, nothing written.
- another fstab line owns /var/disktmp: fail-closed.
- image exists but is not ext4: fail-closed, never reformatted.
- quotactl or remount fails: fail-closed, non-zero exit.
- image fails to mount at boot: fail-open on purpose. nofail keeps the
  boot going and the 1777 directory underneath takes writes uncapped,
  instead of every command that uses it failing. --verify-only exits 1.

Passed in vmbox, not verified on the host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WzxdWW9EDj5WPLpxuWXv29
2026-11-22 11:55:06 +01:00

18 lines
1.5 KiB
JSON

{
"title": "fix_tmp_space.sh: 30G /tmp tmpfs, live user cap, 64G /var/disktmp",
"objective": "Commands stop failing with EDQUOT on /tmp: the tmpfs grows to 30G without an unmount, each logged-in user's cap rises live to 80% of it, and a 64G disk-backed temp area exists at /var/disktmp for heavy writers to use later through TMPDIR.",
"acceptance_criteria": [
"`sudo fix_tmp_space.sh` on a stock machine writes the tmp.mount drop-in, the fstab line and the tmpfiles entry, reloads systemd once, remounts /tmp at size=30G and keeps usrquota, files and X11 sockets in /tmp.",
"Each non-root uid under /run/user gets a cap of 80% of 30G live (25165824 KiB); a cap of 0 or one already within 1 MiB is left alone.",
"/var/disktmp is a mounted 64G sparse ext4 image, mode 1777; a file written there by a user lands in the image.",
"A second run changes nothing and prints one line; --verify-only changes nothing, works without root and exits non-zero on drift.",
"After a reboot /tmp is 30G from the drop-in, systemd applies its own 80% cap at login, and /var/disktmp is mounted and emptied by tmpfiles."
],
"out_of_scope": [
"Pointing heavy writers at /var/disktmp through TMPDIR.",
"/dev/shm and its quota.",
"Running the script on the host (the coordinator does that after review)."
],
"verifier": "test_tmp_space_apply.sh (42 passed), test_tmp_space_verify.sh (36 passed), test_tmp_quota.py (11 passed); every phase of vmbox_tmp_space.sh OK in guest tmpspace, including the reboot and a fail-open boot without the image."
}