summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-09-17 15:39:13 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-09-17 15:39:13 -0400
commit2442281e413cd52f40bedb6a40a67d0e4461bf39 (patch)
treed133c9d625a3fc47b5510c2ba067defec91afcb9
parented447bb22bffd06d8f971b676ab6de7a72977b50 (diff)
parentf9154b0e1bb506d218d429ff132de2b294c2ef9c (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-rw-r--r--doc/forum/git-annex_pre-commit_eats_all_my_4GB_of_ram.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/forum/git-annex_pre-commit_eats_all_my_4GB_of_ram.mdwn b/doc/forum/git-annex_pre-commit_eats_all_my_4GB_of_ram.mdwn
new file mode 100644
index 000000000..82ca06b85
--- /dev/null
+++ b/doc/forum/git-annex_pre-commit_eats_all_my_4GB_of_ram.mdwn
@@ -0,0 +1,24 @@
+Hi all,
+
+git-annex basically renders my repository unmanageble. What is the
+best and save (!) way to recover?
+
+Here is my situation:
+
+I have a fairly large repository with ~8000 managed files taking about
+65GB of disk space.
+
+git-annex worked well there. But some programs choke on the
+symlinks. So, I converted the repository to direct mode. The
+transition worked well.
+
+Now git status reports a type change for the ~8000 files.
+
+But as soon as I run
+
+ git commit -m "typechange" even-only-one-of-the-files
+
+the process `git-annex pre-commit .` eats 3.5GB of ram, where I
+usually kill it, as I only have 4GB of ram....
+
+-- Andreas