docs(FORGE): the 46 GiB is LFS storage, not reachable history (#1507) #1778
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!1778
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/1117-0305"
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?
The space section said the 46.2 GiB in
packetforge-firmwarewas reachable history, and sent the reader togit filter-repo. That reading was wrong, and measured today:sizegit count-objects -vH(full clone, 26 commits)git grep -l "^version https://git-lfs.github.com/spec/v1" HEAD)So the 46.2 GiB is the LFS object store, which the API
sizeincludes 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:
filter-repoas the right tool only whencount-objectsclimbs with the API number and the tip stays small;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.js372 files all OK;scripts/check-doc-citations.jsclean;scripts/check-canonical-urls.jsOK.9249a27a1f0d53a517830d53a5178300252f8977