docs(forge): the disk-full triage block measures at the bind source, not at /data (#1507) #1790
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1790
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/1117-0435"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #1507 (the remaining instance of one defect on the page - the storage decision itself still needs the host).
What was wrong
The first instruction block on
docs/FORGE_TROUBLESHOOTING.md, headed "On the host, in this order", told a host shell to run:/datais the container's mount point - the page records the bind.../forgejo/data -> /dataa few sections below. On the hostdferrors to stderr and thedu, with2>/dev/null, prints nothing and exits 0. The reader sees a blank line and concludes the failed merge attempts left nothing behind, then goes looking for space that is sitting in half-written clones. That is the empty-result-read-as-measurement mistake the later sections of this page exist to correct - #1784 and #1787 fixed it twice further down and left this occurrence, which is the first thing a reader runs.What changed
docker inspect forgejoto name the bind, then loops the two bind sources (/mnt/cache/appdata/forgejo/data,/mnt/user/appdata/forgejo/data), printingabsent: <path>for a candidate that is not there instead of nothing;dfand thedurun at$base/$tmp, where a host shell can see them; the2>/dev/nullnow only silences a glob whose directory was already proved to exist, so silence means "empty", not "wrong path";/mnt/user/...bind is the FUSE view, so itsdfreports the shfs pool and not the disk.Tests
test/forge-space-accounting.test.js- 29 assertions, 0 failed (was 22; 7 new). Four of the new ones are red againstorigin/main's copy of the page. The block is anchored on its unique preceding paragraph, because two sections open with the same sentence and the first version of these assertions read the wrong one.Gates:
scripts/syntax-check.js374 files OK;scripts/check-control-bytes.jsclean;scripts/check-doc-citations.jsclean apart from the two known suspects inSIMULATION.md/UPSTREAM-DESIGN.md. Engine code untouched, so no full suite.Refs #1507 (still blocked on the host:
ssh odinnow demands a Tailscale SSH browser check, so theduthat says which volume holds the 47 GiB cannot be run from here).54db42aef40da80fdc780da80fdc783ce432b3b2