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 (and restore, of course!) 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?
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or just go on silently but keep the other repository intact (or corrupt the other repositories too, but I very much hope not).
But then I also don't know how to fix corruption once I found it. Just running fsck once a day, removing the broken repo and cloning it from somewhere else again doesn't seem very efficient (and what to do, hypothetically, if all my repos were broken, but in different places?).
backup git data-integrity
asked Dec 12 '18 at 16:13
Nobody
1408
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 (and restore, of course!) 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?
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or just go on silently but keep the other repository intact (or corrupt the other repositories too, but I very much hope not).
But then I also don't know how to fix corruption once I found it. Just running fsck once a day, removing the broken repo and cloning it from somewhere else again doesn't seem very efficient (and what to do, hypothetically, if all my repos were broken, but in different places?).
backup git data-integrity
asked Dec 12 '18 at 16:13
Nobody
1408
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 (and restore, of course!) 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?
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or just go on silently but keep the other repository intact (or corrupt the other repositories too, but I very much hope not).
But then I also don't know how to fix corruption once I found it. Just running fsck once a day, removing the broken repo and cloning it from somewhere else again doesn't seem very efficient (and what to do, hypothetically, if all my repos were broken, but in different places?).
backup git data-integrity
asked Dec 12 '18 at 16:13
Nobody
1408
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 (and restore, of course!) 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?
To be more specific, the most pressing question I have is whether pull/push will notice corruption and abort or just go on silently but keep the other repository intact (or corrupt the other repositories too, but I very much hope not).
But then I also don't know how to fix corruption once I found it. Just running fsck once a day, removing the broken repo and cloning it from somewhere else again doesn't seem very efficient (and what to do, hypothetically, if all my repos were broken, but in different places?).
backup git data-integrity
backup git data-integrity
asked Dec 12 '18 at 16:13
Nobody
1408
asked Dec 12 '18 at 16:13
Nobody
1408
edited Dec 26 '18 at 10:57
asked Dec 12 '18 at 16:13
Nobody
1408
asked Dec 12 '18 at 16:13
Nobody
1408
asked Dec 12 '18 at 16:13
Nobody
1408
1408
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
