From 7dba58f694e9d9ac180eca16c29afb1eac3f3108 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 18:16:52 +0000 Subject: [PATCH 1/3] Added a comment --- ..._6c3584ade1ee6cccddddeaa8e1697945._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment diff --git a/doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment b/doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment new file mode 100644 index 0000000000..c7622955bf --- /dev/null +++ b/doc/bugs/TransferScanner_crash_on_Android/comment_1_6c3584ade1ee6cccddddeaa8e1697945._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T18:16:52Z" + content=""" +Wow, that's a lot of NULs! + +Can you drop to a shell and run `git fsck` in the repository? + +I'm guessing that `git annex fsck` is going to fail with some of the same type errors, but you could also try it. + +It seems pretty clear there's damage somewhere. Like something (perhaps a compact flash glitch?) inserted a ton of NULs into the git repository, or corrupted a filename's length field or something. + +--- + +Probably the best thing to do, to get back to a working repository is to move the current repo out of the way, re-setup the assistant on your Android from one of your other repositories (assuming you have another one). Or if this is your only clone of this git repository, you may be able to run `git annex uninit` in it. + +Then if necessary the contents of files can be rescued from `.git/annex/objects/` in the corrupt repository, by running `git annex import` in the new repository and passing it that directory. And finish up with a `git annex fsck`. +"""]] From 798c06f60e2984e6c65e8c14c6f94989a0183f18 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 18:21:18 +0000 Subject: [PATCH 2/3] Added a comment --- ...comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment diff --git a/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment b/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment new file mode 100644 index 0000000000..bf5f04a909 --- /dev/null +++ b/doc/bugs/git_annex_uninit_removes_files_not_previously_added_to_annex/comment_1_ce4e3b1bf0d53119d049cf7dd621c5c4._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T18:21:18Z" + content=""" +I can't reproduce that. uninit leaves alone files that are not checked into git. Indeed, it only ever does anything to files that are checked into git and are symlinks to git-annex content. So I don't see how it could possibly behave as described. + +Please provide a complete transcript of the problem you are seeing. +"""]] From 1a55c015f2cdba65c6be2a762c3f969dae8a2b03 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 16 Jul 2013 18:29:38 +0000 Subject: [PATCH 3/3] Added a comment --- .../comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment diff --git a/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment b/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment new file mode 100644 index 0000000000..f9865ca692 --- /dev/null +++ b/doc/bugs/git_annex_uninit_loses_content_when_interrupted/comment_1_fd9d2abbc90fb4f470b2212bc1f4a2dd._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-16T18:29:37Z" + content=""" +All you have to do to get file1 back is check its symlink back out of git's history. `git checkout file1` should suffice to recover. \"Loses content\" is way overstating the severity of this bug. +"""]]