docs(FORGE): the 46 GiB is LFS storage, not reachable history (#1507) #1778

Merged
jaylouisw merged 1 commit from fix/1117-0305 into main 2026-11-17 03:19:23 +00:00
Owner

The space section said the 46.2 GiB in packetforge-firmware was reachable history, and sent the reader to git filter-repo. That reading was wrong, and measured today:

measurement value
API size 46.2 GiB
git count-objects -vH (full clone, 26 commits) size-pack 4.21 MiB, 19,604 objects
largest blob in history 3.9 MB
tip tree 15.5 MB across 5,891 blobs
blobs that are LFS pointers 5,816 (git grep -l "^version https://git-lfs.github.com/spec/v1" HEAD)
declared by those pointers 56.5 GiB, 5,345 distinct objects, ~47 GiB deduplicated

So the 46.2 GiB is the LFS object store, which the API size includes alongside the git repository. Nothing was committed-then-deleted; the images were never in git. A rewrite would delete 5,816 130-byte pointers and break the manifests, and cannot reclaim a single LFS byte.

Changes:

  • split the attribution three ways (pack / tree / LFS) with pasteable commands, and state the measured split;
  • keep filter-repo as the right tool only when count-objects climbs with the API number and the tip stays small;
  • name the host-side LFS root to du (/data/gitea/lfs, /data/gitea/data/lfs).

test/forge-space-accounting.test.js: 15 assertions; 5 fail on the previous page (LFS check, pointer command, measured counts, rewrite-cannot-reclaim, withdrawn 6.4 MB/7,400 reading).

Refs #1507. The decision itself (delete/prune LFS objects, move LFS storage, grow the volume) still needs the host, so this does not close it.

Gates: scripts/syntax-check.js 372 files all OK; scripts/check-doc-citations.js clean; scripts/check-canonical-urls.js OK.

The space section said the 46.2 GiB in `packetforge-firmware` was reachable history, and sent the reader to `git filter-repo`. That reading was wrong, and measured today: | measurement | value | |---|---| | API `size` | 46.2 GiB | | `git count-objects -vH` (full clone, 26 commits) | **size-pack 4.21 MiB**, 19,604 objects | | largest blob in history | 3.9 MB | | tip tree | 15.5 MB across 5,891 blobs | | blobs that are LFS pointers | 5,816 (`git grep -l "^version https://git-lfs.github.com/spec/v1" HEAD`) | | declared by those pointers | 56.5 GiB, 5,345 distinct objects, ~47 GiB deduplicated | So the 46.2 GiB is the **LFS object store**, which the API `size` includes alongside the git repository. Nothing was committed-then-deleted; the images were never in git. A rewrite would delete 5,816 130-byte pointers and break the manifests, and cannot reclaim a single LFS byte. Changes: - split the attribution three ways (pack / tree / LFS) with pasteable commands, and state the measured split; - keep `filter-repo` as the right tool only when `count-objects` climbs with the API number and the tip stays small; - name the host-side LFS root to `du` (`/data/gitea/lfs`, `/data/gitea/data/lfs`). `test/forge-space-accounting.test.js`: 15 assertions; 5 fail on the previous page (LFS check, pointer command, measured counts, rewrite-cannot-reclaim, withdrawn 6.4 MB/7,400 reading). Refs #1507. The decision itself (delete/prune LFS objects, move LFS storage, grow the volume) still needs the host, so this does not close it. Gates: `scripts/syntax-check.js` 372 files all OK; `scripts/check-doc-citations.js` clean; `scripts/check-canonical-urls.js` OK.
docs(FORGE): the 46 GiB is LFS, not reachable history (#1507)
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 18) (pull_request) Successful in 54s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Server smoke test (pull_request) Successful in 8s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Docker build (pull_request) Successful in 17s
CI / Arm auto-merge (pull_request) Successful in 5s
9249a27a1f
The space section read a 46.2 GiB repository `size` next to a small tip tree and
concluded the bytes were reachable history, then recommended a `git filter-repo`
rewrite. Measured today against packetforge-firmware: the whole git side packs to
4.21 MiB (26 commits, 19,604 objects, largest blob 3.9 MB); the tip tree is 15.5 MB
across 5,891 blobs, and 5,816 of those are LFS pointers declaring 56.5 GiB over
5,345 distinct objects. The API's `size` counts git plus LFS, so the 46.2 GiB is
the LFS object store.

A rewrite would delete 130-byte pointers, break the manifests, and free nothing.
The page now splits the number three ways (pack, tree, LFS) with pasteable
commands, states the measured split, and keeps the rewrite as the right tool only
when count-objects climbs with the API size.

test/forge-space-accounting.test.js: 15 assertions, 5 fail on the previous page.
jaylouisw force-pushed fix/1117-0305 from 9249a27a1f
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Test (Node 18) (pull_request) Successful in 54s
CI / Test (Node 20) (pull_request) Successful in 49s
CI / Server smoke test (pull_request) Successful in 8s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Docker build (pull_request) Successful in 17s
CI / Arm auto-merge (pull_request) Successful in 5s
to 0d53a51783
Some checks failed
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 4s
2026-11-17 03:15:12 +00:00
Compare
jaylouisw force-pushed fix/1117-0305 from 0d53a51783
Some checks failed
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Server smoke test (pull_request) Successful in 10s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Failing after 50s
CI / Test (Node 18) (pull_request) Successful in 1m1s
CI / Test (Node 22) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 4s
to 00252f8977
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 6s
CI / Classify the change (pull_request) Successful in 12s
CI / Test (Node 18) (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Has been skipped
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Arm auto-merge (pull_request) Has been skipped
2026-11-17 03:17:25 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1778
No description provided.