diff options
author | divB <divB@web> | 2014-08-02 20:24:15 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-08-02 20:24:15 +0000 |
commit | be6753d7c1f9dae14e13e0ed9e4af4424a6133fb (patch) | |
tree | 9cc8b4c09079b618020a25a9fceab037d7609cff | |
parent | da37e6553661e2738a69f097886e01d4a019f395 (diff) |
-rw-r--r-- | doc/forum/Pusher_crashed__44___attempt_to_repair_hangs__44___broken_symlinks.mdwn | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/Pusher_crashed__44___attempt_to_repair_hangs__44___broken_symlinks.mdwn b/doc/forum/Pusher_crashed__44___attempt_to_repair_hangs__44___broken_symlinks.mdwn index 91fbfbc7b..f83a85ff4 100644 --- a/doc/forum/Pusher_crashed__44___attempt_to_repair_hangs__44___broken_symlinks.mdwn +++ b/doc/forum/Pusher_crashed__44___attempt_to_repair_hangs__44___broken_symlinks.mdwn @@ -9,6 +9,7 @@ Suddenly weird things started to happen 2.) On Windows, when I get "Pusher crashed: failed to read sha from git write-tree [Restart Thread]". When I click "Restart Thread" nothing happens but the message from (1) persists. 3.) When I run "git annex fsck" on the client I get thousands of messages like + fsck Fotos/2014/DSC_0303.JPG ** No known copies exist of Fotos/2014/DSC_0303.JPG failed |