Skip to content

Update README.md to include block corruption risk caveat #7

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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JaspalSuri
Copy link

From your comment on the Hyperspace thread:

There is one huge caveat I should add to the README - block corruption happens. Having a second copy of a file is a crude form of backup. Cloning causes all instances to use the same block, so if that one instance is corrupted, all clones are. That’s fine for software projects with generated files that can be rebuilt or checked out again, but introduces some risk for files that may not otherwise be replaceable. I keep multiple backups of all that stuff in hardware other than where I’m deduping, so I dedup with abandon.

I asked ChatGPT to rewrite it as a warning. I read it and it seems ok to me. Feel free to make whatever changes you'd like, of course. Sorry for not naming the branch something else.

From [your comment on the Hyperspace thread](https://news.ycombinator.com/item?id=43179652):

> There is one huge caveat I should add to the README - block corruption happens. Having a second copy of a file is a crude form of backup. Cloning causes all instances to use the same block, so if that one instance is corrupted, all clones are. That’s fine for software projects with generated files that can be rebuilt or checked out again, but introduces some risk for files that may not otherwise be replaceable. I keep multiple backups of all that stuff in hardware other than where I’m deduping, so I dedup with abandon.

I asked ChatGPT to rewrite it as a warning. I read it and it seems ok to me. Feel free to make whatever changes you'd like, of course.

Signed-off-by: Jaspal Suri <[email protected]>
@hohle
Copy link
Contributor

hohle commented Feb 26, 2025

Thank you for adding this! I think should go in the SECURITY CONSIDERATIONS section. Maybe a subheading in that section.

This is replicated in the man page as well (the readme is just a formatted man page), but if you don't want to write mdoc, I understand.

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

Successfully merging this pull request may close these issues.

2 participants