mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

promote forum post to bug

Browse source
This commit is contained in:
Joey Hess 2014-03-10 14:04:13 -04:00
parent 448f2f0a0b
commit aab40f02ca
Failed to extract signature
8 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/bugs/enormous_fsck_output_OOM/comment_1_490b8bfe95b01a23408ecb5d63dcd40b._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.172"
subject="comment 1"
date="2014-02-23T18:51:45Z"
content="""
I suspect that git fsck is outputting so many lines about problems that it's taking more memory than it's limited to using to hold them all.
Can you paste the output of: git fsck --no-dangling --no-reflogs
"""]]

10
doc/bugs/enormous_fsck_output_OOM/comment_2_2666c135dd3378cf6301aa4957049fbd._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.172"
subject="comment 2"
date="2014-02-23T19:09:30Z"
content="""
Erm, that output is liable to be big, I only care how many lines and characters of output there are!
git fsck --no-dangling --no-reflogs |wc
"""]]

10
doc/bugs/enormous_fsck_output_OOM/comment_3_dfb169c441215b671f8c971184de3e16._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.172"
subject="comment 3"
date="2014-02-23T19:12:10Z"
content="""
Also, you can build git-annex from source with the RTS options enabled by running `cabal install git-annex --ghc-options=-rtsopts`
(or just build git-repair which has the repository repair parts of git-annex)
"""]]

30
doc/bugs/enormous_fsck_output_OOM/comment_4_19ef90803aa7ce158bce02378e18ea0f._comment Normal file
View file

@ -0,0 +1,30 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnFjuvfPpi1kf6l54bxfFUm0Aw_Gf_IO0o"
nickname="Aaron"
subject="Didn't work"
date="2014-03-01T22:40:36Z"
content="""
Many thanks for your input, Joey.
That didn't seem to work.
$ git fsck --no-dangling --no-reflogs |wc
error: unknown option `no-dangling'
usage: git fsck [options] [<object>...]
-v, --verbose be verbose
--unreachable show unreachable objects
--tags report tags
--root report root nodes
--cache make index objects head nodes
--reflogs make reflogs head nodes (default)
--full also consider packs and alternate objects
--strict enable more strict checking
--lost-found write dangling objects in .git/lost-found
--progress show progress
0 0 0
$ git --version
git version 1.7.9.5
"""]]

12
doc/bugs/enormous_fsck_output_OOM/comment_5_2b5406768fff2834f7aefa76ef949de2._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.146"
subject="comment 5"
date="2014-03-05T16:53:33Z"
content="""
You have an older version of git, which does not support --no-dangling.
git-annex will detect that, and omit the option. This does make it more likely that git fsck is outputing a ton of information, so I continue to think that's the most likely cause of the memory use.
Please verify with: git fsck --no-reflogs |wc
"""]]

18
doc/bugs/enormous_fsck_output_OOM/comment_6_0997f1a94c2fda9fe69824e074011518._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnFjuvfPpi1kf6l54bxfFUm0Aw_Gf_IO0o"
nickname="Aaron"
subject="comment 6"
date="2014-03-08T00:08:22Z"
content="""
That seemed to work, thanks:
$ git fsck --no-reflogs |wc
Checking object directories: 100% (256/256), done.
error: refs/gcrypt/gitception+ does not point to a valid object!
error: refs/remotes/Beta/git-annex does not point to a valid object!
error: refs/remotes/Beta/master does not point to a valid object!
Checking connectivity: 128728, done.
369082 1165340 20898546
Thanks for your help!
"""]]

10
doc/bugs/enormous_fsck_output_OOM/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment Normal file
View file

@ -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>
"""]]