summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar divB <divB@web>2014-08-02 22:57:48 +0000
committerGravatar admin <admin@branchable.com>2014-08-02 22:57:48 +0000
commit08fff19ec1ac464c51c3855198402c8f0ce78058 (patch)
tree5d6031a4797709302170c7eb65baff02f480849a
parent4c173523ae0bbfddb88df364a711fe6109c300b2 (diff)
-rw-r--r--doc/forum/Pusher_crashed__44___attempt_to_repair_hangs__44___broken_symlinks.mdwn7
1 files changed, 4 insertions, 3 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 10fd5d6aa..4c1bcc129 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
@@ -1,6 +1,6 @@
Sorry that I put all this in the same thread but I don't know what happened and how it is related.
-I have just a simple setup: git-annex client with assistant (Windows 7) and on a server (Debian).
+I have just a simple setup: git-annex client with assistant (Windows 7) and on a server (Debian, no assistant).
Suddenly weird things started to happen
@@ -68,9 +68,10 @@ But this file exists, I can read, write and delete to this file manually, there
-
-
Oh no, so desparate :-( Any ideas?
+As it seems the client repository is broken but how can it be then that also files on the server repository get deleted which shouldn't be deleted?
+And how can it be that there are not only broken symlinks but symlinks that have just binary garbage as target and "fsck" returns success?
+
(I am happy to share all log files privately but I do not want to publish them here because they contain sensitive data)