From 069b3715d17e4c6803b6efa1a73ec80871b4e41e Mon Sep 17 00:00:00 2001 From: "jenkin.schibel@286264d9ceb79998aecff0d5d1a4ffe34f8b8421" Date: Fri, 29 Oct 2021 18:24:15 +0000 Subject: [PATCH 1/3] --- ...k_became_readonly_after_really_long_fsck.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/journal.lck_became_readonly_after_really_long_fsck.mdwn diff --git a/doc/forum/journal.lck_became_readonly_after_really_long_fsck.mdwn b/doc/forum/journal.lck_became_readonly_after_really_long_fsck.mdwn new file mode 100644 index 0000000000..7d7f1af6be --- /dev/null +++ b/doc/forum/journal.lck_became_readonly_after_really_long_fsck.mdwn @@ -0,0 +1,16 @@ +i recently ran a git annex fsck --all command on my really large backup drive, the check ran all the way through the night, and suddenly it stopped with this error. after getting this error, i tried running a git annex sync, but got the same (read-only file system) error. does anyone have any insight about how to fix this? Or better yet, what might have happened? + + + SHA256E-s3586436--8d7effd412a3225663569a481a5d2fc51c9bf321316119656ce287efa00d69c7.m4a (checksum...) ok + fsck SHA256E-s502--fa9835b9b4655c834732892eb93a3106cdee52b0b1deabc2912742d05323693b.ini + ** No known copies exist of SHA256E-s502--fa9835b9b4655c834732892eb93a3106cdee52b0b1deabc2912742d05323693b.ini + (Avoid this check by running: git annex dead --key ) + failed + fsck SHA256E-s432681--7a504d72fbbd89c2c05603beb7fedff1d89cc38b6b4a9903f5eabf94dc1f840e.JPG (checksum...) ok + fsck SHA256E-s3092745--e682bd862da64ad7d3a81b7dd54700e1536057f3c83972b452eba5f40037db6b.JPG (checksum...) ok + fsck SHA256E-s306570--d7cab655cb0bbd2de09008888101724d37ceef4060d72ea477cc3cd1d0da20b0.jpg (checksum...) ok + fsck SHA256E-s3814174--00bba1e6cb5d8e295a3299a24921044dc3b5a57a86420d65fe796d5505c41aee.mp4 (checksum...) ok + fsck SHA256E-s2345012--9530b1b32b3b1198c42aa4919a5b34698cc75adc9abf5b7b8ca02f7962c66a25.MOV (checksum...) ok + fsck SHA256E-s42254--cb1ae72d7b3a7bddbf5a93142cc1eed43bb5ceacf8fc3920de7876eafb2ea044.jpg (checksum...) ok + fsck SHA256E-s5619907--a190d2f9805d0c9deb1bacead9ce89b895fc21bf7cef38bcf97a3841693e8c8f.ogg (checksum...) ok + git-annex: .git/annex/journal.lck: openFd: permission denied (Read-only file system) From 00bb88fcb639d6d79c49535bd180b7b5e152e69c Mon Sep 17 00:00:00 2001 From: erewhon Date: Sat, 30 Oct 2021 03:00:05 +0000 Subject: [PATCH 2/3] --- ...it-annex-repair_not_able_to_see_external_remotes.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/git-annex-repair_not_able_to_see_external_remotes.mdwn diff --git a/doc/forum/git-annex-repair_not_able_to_see_external_remotes.mdwn b/doc/forum/git-annex-repair_not_able_to_see_external_remotes.mdwn new file mode 100644 index 0000000000..dc053e69b2 --- /dev/null +++ b/doc/forum/git-annex-repair_not_able_to_see_external_remotes.mdwn @@ -0,0 +1,9 @@ +Hi everybody, + +I have an annex repository on an external hard drive. The repository has been corrupted, I think because the hard drive was disconnected when I was syncing the repo. In any case, I have tried fixing it with git-annex-repair. However, the error messages complain about not being able to read from the remote respositories, even when they are available. + +One possible issue is that I am trying to repair the hard drive from a different computer than it normally runs on. This means that I had to change the URLs for the remotes before running git-annex-repair. They are now what they should be on the current computer but, like I said, they are not recognized when I run git-annex-repair. + +Any thoughts on how to solve this issue? I really appreciate any help. Please let me know if there is more information you need from me. + +Thanks very much. From 8c180cf55b025df42df94db44fba640cb023ff9f Mon Sep 17 00:00:00 2001 From: Lukey Date: Sat, 30 Oct 2021 16:45:52 +0000 Subject: [PATCH 3/3] Added a comment --- .../comment_1_6c094472d7f6f5f0257a445805200a82._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/journal.lck_became_readonly_after_really_long_fsck/comment_1_6c094472d7f6f5f0257a445805200a82._comment diff --git a/doc/forum/journal.lck_became_readonly_after_really_long_fsck/comment_1_6c094472d7f6f5f0257a445805200a82._comment b/doc/forum/journal.lck_became_readonly_after_really_long_fsck/comment_1_6c094472d7f6f5f0257a445805200a82._comment new file mode 100644 index 0000000000..8a1314ad03 --- /dev/null +++ b/doc/forum/journal.lck_became_readonly_after_really_long_fsck/comment_1_6c094472d7f6f5f0257a445805200a82._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 1" + date="2021-10-30T16:45:52Z" + content=""" +This has nothing to do with git-annex. For some reason your file system went read-only, you have to look at your kernel log (`dmesg`) for more details. +"""]]