From 61710e0b8d64ca5a1de0cbd3c803c131008c4223 Mon Sep 17 00:00:00 2001 From: anders7788 Date: Thu, 4 Sep 2014 15:47:24 +0000 Subject: [PATCH] Added a comment: [Solved] --- ...comment_2_9f032e43b132bcad656e1337ab2551ad._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Attempting_to_repair_fails_with_everincreasing_deltas/comment_2_9f032e43b132bcad656e1337ab2551ad._comment diff --git a/doc/forum/Attempting_to_repair_fails_with_everincreasing_deltas/comment_2_9f032e43b132bcad656e1337ab2551ad._comment b/doc/forum/Attempting_to_repair_fails_with_everincreasing_deltas/comment_2_9f032e43b132bcad656e1337ab2551ad._comment new file mode 100644 index 0000000000..c139bd963f --- /dev/null +++ b/doc/forum/Attempting_to_repair_fails_with_everincreasing_deltas/comment_2_9f032e43b132bcad656e1337ab2551ad._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="anders7788" + ip="89.160.15.173" + subject="[Solved]" + date="2014-09-04T15:47:24Z" + content=""" +[Solved] + +The following of the steps at: http://git-annex.branchable.com/tips/what_to_do_when_a_repository_is_corrupted/ provided some clues and I discovered that the disk was broken. But a big thanks to git-annex which made it possible to discover this issue early! +"""]]