summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar joakim.hovlandsvag@ad788ffa13d1ccbf03f2c485653900f8baa33950 <joakimhovlandsvag@web>2015-12-13 09:13:25 +0000
committerGravatar admin <admin@branchable.com>2015-12-13 09:13:25 +0000
commitafe478f39df63fd36650fbc095622bf255d3b8bb (patch)
tree4700b91a3030ed20a86354b0e11907b5495e8a91
parent08414ce68101ea2b19430357a8d307f588ba7b58 (diff)
Added a comment: Repairing ignores disk space issues too
-rw-r--r--doc/bugs/Low_disk_space_corrupts_state/comment_1_d8235498e2206c3b5284455e5c4182b9._comment20
1 files changed, 20 insertions, 0 deletions
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
index 000000000..334a0fd94
--- /dev/null
+++ b/doc/bugs/Low_disk_space_corrupts_state/comment_1_d8235498e2206c3b5284455e5c4182b9._comment
@@ -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
+
+"""]]