From 1a9b31ea0a8f855bdf433b48e2f415edb97cfd9c Mon Sep 17 00:00:00 2001 From: Mitchell-Johnson Date: Sun, 25 Oct 2026 21:01:59 -0700 Subject: [PATCH] PLAN: handle fuse.mergerfs (grid's landing pool) in Storage Co-Authored-By: Claude Opus 5.5 --- PLAN.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/PLAN.md b/PLAN.md index 181b765..138608d 100644 --- a/PLAN.md +++ b/PLAN.md @@ -1001,6 +1001,11 @@ what it has moved. ## To do +- **Handle `fuse.mergerfs` in the Storage view** (2026-10-25). `grid` has a mergerfs pool at + `/srv/tank` (the NVMe landing area + `/tank`; `hamlet`'s `docs/tank-landing-plan.md`). + `fuse.mergerfs` isn't in `remoteFS` or `pseudoFS` (`internal/metrics/metrics.go`), so it shows + as a local filesystem whose size is `tank` and the NVMe added together. That counts both twice + in any storage total. Show it, labelled as a pool of its branches, and leave it out of totals. - **Grow the Files tab** — asked for 2026-09-23 as two items (Files polish, and deprecating copyparty), merged 2026-09-24. **copyparty was retired 2026-10-11** at Mitchell's call, ahead of these gaps rather than after them: service, files and NPM host all gone, with a