From 6f07a82f9cc95add863305bdd4e828b80990364e Mon Sep 17 00:00:00 2001 From: "contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" Date: Sun, 14 Nov 2021 18:33:52 +0000 Subject: [PATCH 1/5] --- doc/bugs/fsck_always_fails.mdwn | 50 +++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 doc/bugs/fsck_always_fails.mdwn diff --git a/doc/bugs/fsck_always_fails.mdwn b/doc/bugs/fsck_always_fails.mdwn new file mode 100644 index 0000000000..e225e8b77f --- /dev/null +++ b/doc/bugs/fsck_always_fails.mdwn @@ -0,0 +1,50 @@ +### Please describe the problem. + +All my files added to my archive repo over the past few months seem to fail git annex fsck. + +### What steps will reproduce the problem? + +- Add a file to the repo +- Fsck it + +### What version of git-annex are you using? On what operating system? + +8.20211012-geb95ed486 on Arch Linux directly downloaded from this website +I was using some older version from 2020 previously + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + jookia@titan:/data/jookia/archive% head -c1024 /dev/urandom > RANDOM.TEST (exited 130) (1 jobs) 05:27 + jookia@titan:/data/jookia/archive% git annex add RANDOM.TEST (1 jobs) 05:27 + add RANDOM.TEST + ok + (recording state in git...) + jookia@titan:/data/jookia/archive% git commit -m RANDOM.TEST (1 jobs) 05:27 + [main 2e9f2429018] RANDOM.TEST + 1 file changed, 1 insertion(+) + create mode 120000 RANDOM.TEST + jookia@titan:/data/jookia/archive% git annex fsck RANDOM.TEST (1 jobs) 05:27 + + Remote black cannot currently be accessed. + Warning: Fscking a repository that is currently marked as dead. + fsck RANDOM.TEST (checksum...) + ** No known copies exist of RANDOM.TEST + These dead repositories used to have copies + e62ad85d-368d-4ea5-a85c-e94598904a50 -- T400 laptop [here] + failed + (recording state in git...) + fsck: 1 failed + jookia@titan:/data/jookia/archive% ls -l RANDOM.TEST (exited 130) (1 jobs) 05:28 + lrwxrwxrwx 1 jookia jookia 194 Nov 15 05:27 RANDOM.TEST -> .git/annex/objects/K4/jV/SHA256E-s1024--0dedc9e7fb3fa053982201c2166fc1265ebd64d41ab91fe1c348c2df46f50167.TEST/SHA256E-s1024--0dedc9e7fb3fa053982201c2166fc1265ebd64d41ab91fe1c348c2df46f50167.TEST + jookia@titan:/data/jookia/archive% sha256sum RANDOM.TEST (1 jobs) 05:28 + 0dedc9e7fb3fa053982201c2166fc1265ebd64d41ab91fe1c348c2df46f50167 RANDOM.TEST +# End of transcript or log. +"""]] + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +Yes, I've been using it for years. It's a robust and reliable piece of software. :) From 0c4a40d59fa1bd211b3f811be24144fae2037df3 Mon Sep 17 00:00:00 2001 From: "contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" Date: Sun, 14 Nov 2021 18:35:45 +0000 Subject: [PATCH 2/5] Added a comment --- ...comment_1_d0620c59d6ada267792d0cde7b3c43f3._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/fsck_always_fails/comment_1_d0620c59d6ada267792d0cde7b3c43f3._comment diff --git a/doc/bugs/fsck_always_fails/comment_1_d0620c59d6ada267792d0cde7b3c43f3._comment b/doc/bugs/fsck_always_fails/comment_1_d0620c59d6ada267792d0cde7b3c43f3._comment new file mode 100644 index 0000000000..bb468c553a --- /dev/null +++ b/doc/bugs/fsck_always_fails/comment_1_d0620c59d6ada267792d0cde7b3c43f3._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" + nickname="contact" + avatar="http://cdn.libravatar.org/avatar/4aa4d7a441bd4e6948fc0012c7229d01" + subject="comment 1" + date="2021-11-14T18:35:45Z" + content=""" +I'm confused as to why it says random data is in an old repository. +numcopies 0 seems to 'fix' this? +"""]] From 0e3fb1c2db416d53316a9a6e6ec9fc5f44d64e4c Mon Sep 17 00:00:00 2001 From: "contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" Date: Sun, 14 Nov 2021 18:37:05 +0000 Subject: [PATCH 3/5] Added a comment --- .../comment_2_b56c7aaf88535830a9f153bba27ececd._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/fsck_always_fails/comment_2_b56c7aaf88535830a9f153bba27ececd._comment diff --git a/doc/bugs/fsck_always_fails/comment_2_b56c7aaf88535830a9f153bba27ececd._comment b/doc/bugs/fsck_always_fails/comment_2_b56c7aaf88535830a9f153bba27ececd._comment new file mode 100644 index 0000000000..42ac2a6230 --- /dev/null +++ b/doc/bugs/fsck_always_fails/comment_2_b56c7aaf88535830a9f153bba27ececd._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" + nickname="contact" + avatar="http://cdn.libravatar.org/avatar/4aa4d7a441bd4e6948fc0012c7229d01" + subject="comment 2" + date="2021-11-14T18:37:04Z" + content=""" +Uh, addendum 2: I signed in with my email which is contact@jookia.org , but it's created a user named 'contact'. Sorry for eating up this username. :) +"""]] From db4ae6c6978afa75f9ae4d1c2133345f7982dca8 Mon Sep 17 00:00:00 2001 From: "contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" Date: Sun, 14 Nov 2021 18:41:18 +0000 Subject: [PATCH 4/5] Added a comment --- ...comment_3_aa0e5955253e94863479d66aedd9d430._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/fsck_always_fails/comment_3_aa0e5955253e94863479d66aedd9d430._comment diff --git a/doc/bugs/fsck_always_fails/comment_3_aa0e5955253e94863479d66aedd9d430._comment b/doc/bugs/fsck_always_fails/comment_3_aa0e5955253e94863479d66aedd9d430._comment new file mode 100644 index 0000000000..909fc888dd --- /dev/null +++ b/doc/bugs/fsck_always_fails/comment_3_aa0e5955253e94863479d66aedd9d430._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="contact@ee563aaec1e9de7a4e8d748992963dba79178e9c" + nickname="contact" + avatar="http://cdn.libravatar.org/avatar/4aa4d7a441bd4e6948fc0012c7229d01" + subject="comment 3" + date="2021-11-14T18:41:18Z" + content=""" +Sorry for the comment spam. It looks like 'Warning: Fscking a repository that is currently marked as dead.' is what was happening here. +The error message is confusing making it seem like the checksum failed and that the file existed elsewhere, not that there's no copies. +"""]] From b4052cb7651c442ba68fe37853c2402b0991d959 Mon Sep 17 00:00:00 2001 From: Lukey Date: Sun, 14 Nov 2021 20:11:35 +0000 Subject: [PATCH 5/5] Added a comment --- .../comment_4_81ccdf94101f1080521d36aa90a376ac._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/fsck_always_fails/comment_4_81ccdf94101f1080521d36aa90a376ac._comment diff --git a/doc/bugs/fsck_always_fails/comment_4_81ccdf94101f1080521d36aa90a376ac._comment b/doc/bugs/fsck_always_fails/comment_4_81ccdf94101f1080521d36aa90a376ac._comment new file mode 100644 index 0000000000..8126445061 --- /dev/null +++ b/doc/bugs/fsck_always_fails/comment_4_81ccdf94101f1080521d36aa90a376ac._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 4" + date="2021-11-14T20:11:35Z" + content=""" +Well, you somehow marked the repo you're working in as dead. Usually you only mark a repo that is irretrievably lost (due to drive failure for example) as dead so git-annex knows that none of the data in it exists anymore and doesn't count it as a copy anymore. That's exactly what you're seeing here. +"""]]