Skip to content

implement re-chunking for borg2 transfer? #8706

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

Open
ThomasWaldmann opened this issue Mar 26, 2025 · 0 comments
Open

implement re-chunking for borg2 transfer? #8706

ThomasWaldmann opened this issue Mar 26, 2025 · 0 comments

Comments

@ThomasWaldmann
Copy link
Member

ThomasWaldmann commented Mar 26, 2025

Considering the CDC fingerprinting issues, we may choose to change how the chunker works, so it would cut chunks differently.

The problem with that is that this breaks deduplication with existing repository contents (chunks that were cut the old way), potentially doubling the repo storage needs.

Obviously, this is problematic as many people might run out of space.

When transferring repo contents to borg2, people will need to arrange new borg2 repos (and additional space for them) anyway, so that might be the perfect time to re-chunk with a new chunker.

So, borg2 transfer could maybe re-use some existing code we already have in borg recreate.

Note: even if we don't add a new chunker, this would be also useful if users want to change the parameters of the existing chunker.

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

No branches or pull requests

1 participant