Added a comment: Repairing ignores disk space issues too
authorjoakim.hovlandsvag@ad788ffa13d1ccbf03f2c485653900f8baa33950 <joakimhovlandsvag@web>
Sun, 13 Dec 2015 09:13:25 +0000 (09:13 +0000)
committeradmin <admin@branchable.com>
Sun, 13 Dec 2015 09:13:25 +0000 (09:13 +0000)
doc/bugs/Low_disk_space_corrupts_state/comment_1_d8235498e2206c3b5284455e5c4182b9._comment [new file with mode: 0644]

diff --git a/doc/bugs/Low_disk_space_corrupts_state/comment_1_d8235498e2206c3b5284455e5c4182b9._comment b/doc/bugs/Low_disk_space_corrupts_state/comment_1_d8235498e2206c3b5284455e5c4182b9._comment
new file mode 100644 (file)
index 0000000..334a0fd
--- /dev/null
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joakim.hovlandsvag@ad788ffa13d1ccbf03f2c485653900f8baa33950"
+ nickname="joakim.hovlandsvag"
+ subject="Repairing ignores disk space issues too"
+ date="2015-12-13T09:13:24Z"
+ content="""
+It seems that `git annex repair` also ignores such issues:
+
+    $ git annex repair
+    Running git fsck ...
+    Initialized empty Git repository in /tmp/tmprepo.0/.git/
+    Trying to recover missing objects from remote home.
+    Unpacking all pack files.
+    error: file write error (No space left on device)
+    fatal: unable to write sha1 file
+    Successfully recovered repository!
+    You should run \"git fsck\" to make sure, but it looks like everything was recovered ok.
+    ok
+
+"""]]