Delete nextcloud/data/*-old-ssd rollback copies (hdd-bulk migration) #37
Labels
No labels
blocked
borg-backup
ceph
forgejo
in-progress
infra
netdata
nextcloud
p:high
p:low
p:medium
searxng
service-onboard
swarm-nodes
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
copper/ccnet-prod-devops#37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Nextcloud's per-user data directories were migrated from
swarm-datatohdd-bulk(USB HDD tier) on 2026-07-19, keeping the pre-migration copies as<user>-old-ssdonswarm-dataas a rollback net (same pattern as the swarm-nvme migration, issue #6).Delete once the hdd-bulk copies have proven stable for ~1-2 weeks (target: ~2026-08-02):
This is what actually reclaims the ~332GiB on
swarm-data.Done — closing.
Verified on the filesystem: no
*-old-ssddirectories remain under/mnt/swarm-data/nextcloud/data, andswarm-datahas drained to 1.7 GiB stored (from ~31 GiB), so the space was reclaimed.Overtaken by events in the meantime: Nextcloud's
datamoved again on 2026-08-08, fromhdd-bulkto the newswarm-data-ecEC 4+2 pool, and the USB HDD tier was decommissioned entirely (pool deleted, OSDs removed, drives pulled). Current state isdataonswarm-data-ec— 408 GiB stored / 601 GiB raw, a 1.47x ratio — confirmed by readingceph.file.layout.poolon a real file. That migration's own rollback copy (data-hdd-old) has also been deleted.