PLAN: handle fuse.mergerfs (grid's landing pool) in Storage
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
695e4c4f57
commit
1a9b31ea0a
@@ -1001,6 +1001,11 @@ what it has moved.
|
|||||||
|
|
||||||
## To do
|
## 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
|
- **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,
|
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
|
ahead of these gaps rather than after them: service, files and NPM host all gone, with a
|
||||||
|
|||||||
Reference in New Issue
Block a user