Garbage Collector need to remove subdirs of storage/shares when deleting shares #1194
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1194
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
As discussed with Warner on IRC,
When GC deletes shares on the grid, it doesn't remove prefixdir and storageindex-dir.
The munin plugin tahoe_files counts storageindex-dir to know how many files are on the Grid.
The count is not correct because empty subdirs are present on
storage/shares/
.In particular, when a share lives in
BASEDIR/storage/shares/PREFIXDIR/SIDIR/SHNUM
(e.g.node-1/storage/shares/d5/d5j2wyxwvrwiftiwvujhozu67i/3
), if we delete the last share in the SIDIR, then we should also delete the SIDIR (but leave the PREFIXDIR), e.g. leavenode-1/storage/shares/d5
but delete everything below that.This requires code in
allmydata.storage.immutable.ShareFile.unlink
andallmydata.storage.mutable.MutableShareFile.unlink
to look in the parent directory, see if it's empty, and if so unlink the parent.