summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar anders7788 <anders7788@web>2014-09-04 15:47:24 +0000
committerGravatar admin <admin@branchable.com>2014-09-04 15:47:24 +0000
commit37a6ba9191fe4e3a41c842b93a5ed5919accb5ea (patch)
tree274f09202aeca6cc861215f419ad045fe11b5ffc
parentbafcca7425f109ac7b8939c50a01df37c339e817 (diff)
Added a comment: [Solved]
-rw-r--r--doc/forum/Attempting_to_repair_fails_with_everincreasing_deltas/comment_2_9f032e43b132bcad656e1337ab2551ad._comment10
1 files changed, 10 insertions, 0 deletions
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 000000000..c139bd963
--- /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!
+"""]]