error: pack-objects died of signal 9517 when trying to re-write history
up vote
0
down vote
favorite
A git repository that I'm interacting with has a huge package file (1.7Gb!) so I've tried to follow this post. I was able to use git filter-branch
, but when I run git gc --aggressive --prune=now
I get:
$ git gc --aggressive --prune=now
Counting objects: 119622, done.
Delta compression using up to 4 threads.
error: pack-objects died of signal 9517)
error: failed to run repack
I tried to lower the threads to 2 and 1 already using git config --global pack.threads "2"
but it didn't help.
Thanks!
git git-gc git-history
add a comment |
up vote
0
down vote
favorite
A git repository that I'm interacting with has a huge package file (1.7Gb!) so I've tried to follow this post. I was able to use git filter-branch
, but when I run git gc --aggressive --prune=now
I get:
$ git gc --aggressive --prune=now
Counting objects: 119622, done.
Delta compression using up to 4 threads.
error: pack-objects died of signal 9517)
error: failed to run repack
I tried to lower the threads to 2 and 1 already using git config --global pack.threads "2"
but it didn't help.
Thanks!
git git-gc git-history
Try to increase memory for packing.
– phd
Nov 22 at 20:58
This is actually died of signal 9. The517)
is left over from earlier text, thatgit pack-objects
was planning to overwrite when something killedgit pack-objects
, probably the OOM killer.
– torek
Nov 23 at 0:47
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
A git repository that I'm interacting with has a huge package file (1.7Gb!) so I've tried to follow this post. I was able to use git filter-branch
, but when I run git gc --aggressive --prune=now
I get:
$ git gc --aggressive --prune=now
Counting objects: 119622, done.
Delta compression using up to 4 threads.
error: pack-objects died of signal 9517)
error: failed to run repack
I tried to lower the threads to 2 and 1 already using git config --global pack.threads "2"
but it didn't help.
Thanks!
git git-gc git-history
A git repository that I'm interacting with has a huge package file (1.7Gb!) so I've tried to follow this post. I was able to use git filter-branch
, but when I run git gc --aggressive --prune=now
I get:
$ git gc --aggressive --prune=now
Counting objects: 119622, done.
Delta compression using up to 4 threads.
error: pack-objects died of signal 9517)
error: failed to run repack
I tried to lower the threads to 2 and 1 already using git config --global pack.threads "2"
but it didn't help.
Thanks!
git git-gc git-history
git git-gc git-history
asked Nov 22 at 15:11
DrDark
60128
60128
Try to increase memory for packing.
– phd
Nov 22 at 20:58
This is actually died of signal 9. The517)
is left over from earlier text, thatgit pack-objects
was planning to overwrite when something killedgit pack-objects
, probably the OOM killer.
– torek
Nov 23 at 0:47
add a comment |
Try to increase memory for packing.
– phd
Nov 22 at 20:58
This is actually died of signal 9. The517)
is left over from earlier text, thatgit pack-objects
was planning to overwrite when something killedgit pack-objects
, probably the OOM killer.
– torek
Nov 23 at 0:47
Try to increase memory for packing.
– phd
Nov 22 at 20:58
Try to increase memory for packing.
– phd
Nov 22 at 20:58
This is actually died of signal 9. The
517)
is left over from earlier text, that git pack-objects
was planning to overwrite when something killed git pack-objects
, probably the OOM killer.– torek
Nov 23 at 0:47
This is actually died of signal 9. The
517)
is left over from earlier text, that git pack-objects
was planning to overwrite when something killed git pack-objects
, probably the OOM killer.– torek
Nov 23 at 0:47
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433822%2ferror-pack-objects-died-of-signal-9517-when-trying-to-re-write-history%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try to increase memory for packing.
– phd
Nov 22 at 20:58
This is actually died of signal 9. The
517)
is left over from earlier text, thatgit pack-objects
was planning to overwrite when something killedgit pack-objects
, probably the OOM killer.– torek
Nov 23 at 0:47