summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-03-10 18:02:46 +0000
committerGravatar admin <admin@branchable.com>2014-03-10 18:02:46 +0000
commit299ae1f68e70c85cffc5e92b0bd4581f7642f54f (patch)
tree1251ef593e8f6d5756726c42855ed877ec93ee2e
parent097450490fafa1dfb06c476db3510eb4e0d0310d (diff)
Added a comment
-rw-r--r--doc/forum/Too_big_to_fsck/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/Too_big_to_fsck/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment b/doc/forum/Too_big_to_fsck/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment
new file mode 100644
index 000000000..14bdc17b8
--- /dev/null
+++ b/doc/forum/Too_big_to_fsck/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="108.236.230.124"
+ subject="comment 7"
+ date="2014-03-10T18:02:46Z"
+ content="""
+Ok, that verifies my hypothesis that fsck is outputting a lot of lines. 369082 lines to be precise, comprising 20 mb of data in all. So it's not too surprising this ends up blowing up into a bad amount of memory use.
+
+I'm going to move this from a forum post over to a bug: <http://git-annex.branchable.com/bugs/enormous_fsck_output_OOM>
+"""]]