Added a comment

This commit is contained in:
Atemu 2021-05-12 14:17:06 +00:00 committed by admin
parent 20af8b311a
commit 9e8e747654

View file

@ -0,0 +1,73 @@
[[!comment format=mdwn
username="Atemu"
avatar="http://cdn.libravatar.org/avatar/d1f0f4275931c552403f4c6707bead7a"
subject="comment 3"
date="2021-05-12T14:17:05Z"
content="""
The weird thing is, this only ever happens with my Documents git-annex repo, the only one where I use the assistant. It has never happened in 4 years of actively using regular git nor my manually committed and synced git-annex repos.
Another corruption just occured but this time on the MBP:
```
[2021-05-11 08:04:43.038047] main: starting assistant version 8.20210330
[2021-05-11 08:04:43.169107] Cronner: Consistency check in progress
[2021-05-11 08:04:43.175482] TransferScanner: Syncing with SOTERIA
(scanning...) [2021-05-11 08:04:43.340744] Watcher: Performing startup scan
(recording state in git...)
(recording state in git...)
(recovering from race...)
To ssh://192.168.101.24/~/Annex/Documents.git/
7b587c48b..4c7b284c5 git-annex -> synced/git-annex
[2021-05-11 08:04:47.087899] Cronner: Attempting to repair MB-<REDACTED> [here]
Watcher crashed: PauseWatcher
[2021-05-11 08:04:47.138205] Watcher: warning Watcher crashed: PauseWatcher
Unpacking all pack files.
fatal: early EOF
[2021-05-11 08:05:27.149344] main: starting assistant version 8.20210330
[2021-05-11 08:05:27.325057] Cronner: Consistency check in progress
(recording state in git...)
error: invalid object 100644 f30c0963ac4560878ae6803608310c289de30e26 for '319/854/SHA256E-s1400--dd4744948961710e8369365e439bb37013c5664ed6d8e58ef21a855a08ff4108.o.log'
fatal: git-write-tree: error building trees
.git-annex-wrapped: failed to read sha from git write-tree
CallStack (from HasCallStack):
error, called at ./Git/Sha.hs:23:15 in main:Git.Sha
[2021-05-11 08:05:28.719256] TransferScanner: Syncing with SOTERIA
(recording state in git...)
error: invalid object 100644 f30c0963ac4560878ae6803608310c289de30e26 for '319/854/SHA256E-s1400--dd4744948961710e8369365e439bb37013c5664ed6d8e58ef21a855a08ff4108.o.log'
fatal: git-write-tree: error building trees
Merger crashed: failed to read sha from git write-tree
CallStack (from HasCallStack):
error, called at ./Git/Sha.hs:23:15 in main:Git.Sha
[2021-05-11 08:05:28.905248] Merger: warning Merger crashed: failed to read sha from git write-tree
CallStack (from HasCallStack):
error, called at ./Git/Sha.hs:23:15 in main:Git.Sha
Auto packing the repository in background for optimum performance.
See \"git help gc\" for manual housekeeping.
error: Could not read d3720891bb000797d5fba08403540f8db208fd7a
error: Could not read 0fa98c99e87fd34202e68016c39f7ba00b7e3e1a
error: Could not read 0fa98c99e87fd34202e68016c39f7ba00b7e3e1a
error: Could not read 0fa98c99e87fd34202e68016c39f7ba00b7e3e1a
error: Could not read d3720891bb000797d5fba08403540f8db208fd7a
error: Could not read 0fa98c99e87fd34202e68016c39f7ba00b7e3e1a
error: Could not read d3720891bb000797d5fba08403540f8db208fd7a
error: Could not read 0fa98c99e87fd34202e68016c39f7ba00b7e3e1a
error: Could not read d3720891bb000797d5fba08403540f8db208fd7a
(recording state in git...)
error: invalid object 100644 f30c0963ac4560878ae6803608310c289de30e26 for '319/854/SHA256E-s1400--dd4744948961710e8369365e439bb37013c5664ed6d8e58ef21a855a08ff4108.o.log'
fatal: git-write-tree: error building trees
TransferScanner crashed: failed to read sha from git write-tree
CallStack (from HasCallStack):
error, called at ./Git/Sha.hs:23:15 in main:Git.Sha
[2021-05-11 08:05:29.430437] TransferScanner: warning TransferScanner crashed: failed to read sha from git write-tree
CallStack (from HasCallStack):
error, called at ./Git/Sha.hs:23:15 in main:Git.Sha
[2021-05-11 08:05:52.410361] main: warning git-annex has been shut down
```
This happened just after I started the assistant/webapp and you can see that I shut it down in the end.
My filesystems are ZFS on the Linux machine and APFS on the MBP. Being an Apple product, I'd expect APFS to be built to high standards (though I don't fully trust it) but ZFS corrupting anything or losing data is almost unheard of.
I'll try setting `core.fsyncObjectFiles` on this repo and update this issue accordingly when I see another corruption with it on. Shouldn't take too long as this occurs worringly frequently.
Btw, repair always fails in my setup because git seems to be unable to find the `SOTERIA` remote; is it trying to use the remote name literally as an address perhaps?
"""]]