Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gc doesn't know about by-sha256 #10

Open
allisonkarlitskaya opened this issue Oct 15, 2024 · 1 comment
Open

gc doesn't know about by-sha256 #10

allisonkarlitskaya opened this issue Oct 15, 2024 · 1 comment

Comments

@allisonkarlitskaya
Copy link
Collaborator

Running gc in the presence of by-sha256 splitstreams gives:

Error: category directory contains non-symlink

Which is probably for the best, because it doesn't know about them and would probably decide to delete them if it could find them.

We should do something sensible there. I wonder if we should take a more generic approach to symlink handling: all symlinks reachable from anything under */refs/** get to live. We can better do the checking about if the structure is correct from fsck.

@allisonkarlitskaya
Copy link
Collaborator Author

by-sha256 got axed, but we still need to update the GC code to understand that the symlinks directly in streams/ are now body sha256.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant