From 47ad76d1105eda38ccc9917ce7bc1886d5aa89d0 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus" Date: Tue, 24 Jul 2012 19:08:11 +0000 Subject: --- doc/forum/Fixing_up_corrupt_annexes.mdwn | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Fixing_up_corrupt_annexes.mdwn diff --git a/doc/forum/Fixing_up_corrupt_annexes.mdwn b/doc/forum/Fixing_up_corrupt_annexes.mdwn new file mode 100644 index 000000000..be6beeca8 --- /dev/null +++ b/doc/forum/Fixing_up_corrupt_annexes.mdwn @@ -0,0 +1,10 @@ +I was wondering how does one recover from... + +
+(Recording state in git...)
+error: invalid object 100644 8f154c946adc039af5240cc650a0a95c840e6fa6 for '041/5a4/SHA256-s6148--7ddcf853e4b16e77ab8c3c855c46867e6ed61c7089c334edf98bbdd3fb3a89ba.log'
+fatal: git-write-tree: error building trees
+git-annex: failed to read sha from git write-tree
+
+ +The above was caught when i ran a "git annex fsck --fast" to check stash of files" -- cgit v1.2.3 From b5b0ae6f3e1c9edead1e697f401f7670a93d710a Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 24 Jul 2012 22:00:36 +0000 Subject: Added a comment --- .../comment_1_cea21f96bcfb56aaab7ea03c1c804d2d._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/forum/Fixing_up_corrupt_annexes/comment_1_cea21f96bcfb56aaab7ea03c1c804d2d._comment diff --git a/doc/forum/Fixing_up_corrupt_annexes/comment_1_cea21f96bcfb56aaab7ea03c1c804d2d._comment b/doc/forum/Fixing_up_corrupt_annexes/comment_1_cea21f96bcfb56aaab7ea03c1c804d2d._comment new file mode 100644 index 000000000..335cbb51d --- /dev/null +++ b/doc/forum/Fixing_up_corrupt_annexes/comment_1_cea21f96bcfb56aaab7ea03c1c804d2d._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + subject="comment 1" + date="2012-07-24T22:00:35Z" + content=""" +This is a corrupt git repository. See [[tips/what_to_do_when_a_repository_is_corrupted]] +"""]] -- cgit v1.2.3