How to handle bit rot in git repositories?
As confirmed by this question, git does not automatically protect against bit rot. There was a link given there for a git file system check, but it's not obvious from that what my backup strategy should be.
I have to admit I'm this kind of git user:
Could someone explain to me a simple strategy for keeping the files I store in git repos intact over the long term?
- It's safe to assume I have at least 3 copies of a repository.
- Some of the copies are less likely to have bit rot than others and I have a general idea of the probabilities.
- I don't just use git for code, there are all kinds of binary and text files in my repositories (I use git for all my important files to sync between different computers and backup discs. Otherwise I would quickly make a mess of it. I know that's not what git is intended for. It works fine though, other than I recently read claims that bit rot is a relevant problem).
- I don't read the relevant system logs. I do read the output of commands I run.
- Some of the repositories are bare, others include a working tree.
- For some files I also have a copy not in git
- No I don't have another backup strategy that already verifies the repos on a lower level and don't want to get one. Git is my backup strategy. A file not committed to a git repo is not a file that I would be devastated to lose.
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or corrupt the other repositories too.
backup git data-integrity
add a comment |
As confirmed by this question, git does not automatically protect against bit rot. There was a link given there for a git file system check, but it's not obvious from that what my backup strategy should be.
I have to admit I'm this kind of git user:
Could someone explain to me a simple strategy for keeping the files I store in git repos intact over the long term?
- It's safe to assume I have at least 3 copies of a repository.
- Some of the copies are less likely to have bit rot than others and I have a general idea of the probabilities.
- I don't just use git for code, there are all kinds of binary and text files in my repositories (I use git for all my important files to sync between different computers and backup discs. Otherwise I would quickly make a mess of it. I know that's not what git is intended for. It works fine though, other than I recently read claims that bit rot is a relevant problem).
- I don't read the relevant system logs. I do read the output of commands I run.
- Some of the repositories are bare, others include a working tree.
- For some files I also have a copy not in git
- No I don't have another backup strategy that already verifies the repos on a lower level and don't want to get one. Git is my backup strategy. A file not committed to a git repo is not a file that I would be devastated to lose.
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or corrupt the other repositories too.
backup git data-integrity
add a comment |
As confirmed by this question, git does not automatically protect against bit rot. There was a link given there for a git file system check, but it's not obvious from that what my backup strategy should be.
I have to admit I'm this kind of git user:
Could someone explain to me a simple strategy for keeping the files I store in git repos intact over the long term?
- It's safe to assume I have at least 3 copies of a repository.
- Some of the copies are less likely to have bit rot than others and I have a general idea of the probabilities.
- I don't just use git for code, there are all kinds of binary and text files in my repositories (I use git for all my important files to sync between different computers and backup discs. Otherwise I would quickly make a mess of it. I know that's not what git is intended for. It works fine though, other than I recently read claims that bit rot is a relevant problem).
- I don't read the relevant system logs. I do read the output of commands I run.
- Some of the repositories are bare, others include a working tree.
- For some files I also have a copy not in git
- No I don't have another backup strategy that already verifies the repos on a lower level and don't want to get one. Git is my backup strategy. A file not committed to a git repo is not a file that I would be devastated to lose.
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or corrupt the other repositories too.
backup git data-integrity
As confirmed by this question, git does not automatically protect against bit rot. There was a link given there for a git file system check, but it's not obvious from that what my backup strategy should be.
I have to admit I'm this kind of git user:
Could someone explain to me a simple strategy for keeping the files I store in git repos intact over the long term?
- It's safe to assume I have at least 3 copies of a repository.
- Some of the copies are less likely to have bit rot than others and I have a general idea of the probabilities.
- I don't just use git for code, there are all kinds of binary and text files in my repositories (I use git for all my important files to sync between different computers and backup discs. Otherwise I would quickly make a mess of it. I know that's not what git is intended for. It works fine though, other than I recently read claims that bit rot is a relevant problem).
- I don't read the relevant system logs. I do read the output of commands I run.
- Some of the repositories are bare, others include a working tree.
- For some files I also have a copy not in git
- No I don't have another backup strategy that already verifies the repos on a lower level and don't want to get one. Git is my backup strategy. A file not committed to a git repo is not a file that I would be devastated to lose.
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or corrupt the other repositories too.
backup git data-integrity
backup git data-integrity
asked Dec 12 at 16:13
Nobody
1428
1428
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383025%2fhow-to-handle-bit-rot-in-git-repositories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383025%2fhow-to-handle-bit-rot-in-git-repositories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown