followup

doc/bugs/git-annex_upgrade_fails/comment_1_244e7e1cc7c1717ecf60591f81eee7e3._comment

@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2019-08-29T16:24:37Z"
+ content="""
+git status exiting with -9 means it died of SIGKILL.
+The only thing I can think of that could have killed it is the OOM killer.
+
+Based on your apt config, I guess git was probably older than version 2.23,
+so it would have the [[bug that makes git status use a lot of memory|v7_unlock_big_file__58___out_of_memory]].
+
+It appears that the v5 repository was a direct mode repository.
+
+What I suggest you do to recover is, upgrade git to 2.23, and re-run
+git-annex upgrade. It should pick up where it left off.
+"""]]

doc/bugs/git-annex_upgrade_fails/comment_2_1ed5217d2e4997df237256dbc4bd350e._comment

@@ -0,0 +1,26 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2019-08-29T16:54:35Z"
+ content="""
+I reproduced the problem using git 2.1.4. The error message was slightly
+better:
+
+	$ git annex upgrade
+	upgrade (v5 to v6...) (scanning for unlocked files...)
+	(v6 to v7...) ok
+	(recording state in git...)
+	fatal: Out of memory? mmap failed: Cannot allocate memory
+	
+	git status will show some files to be modified, since content availability has changed and git-annex was unable to update the index. This is only a cosmetic problem affecting git status; git add, git commit, etc won't be affected. To fix the git status display, you can run: git update-index -q --refresh <file>
+	$ git status
+	fatal: Out of memory? mmap failed: Cannot allocate memory
+
+And with the newer git, resuming the failed upgrade did succeed:
+
+	$ git status
+	On branch adjusted/master(unlocked)
+	nothing to commit, working tree clean
+	$ git annex upgrade
+	upgrade ok
+"""]]