Git克隆:索引包因信号25死亡 [英] Git clone: index-pack died of signal 25

问题描述

当我尝试克隆特定存储库时，显示以下错误消息.仅在克隆该存储库时才会发生这种情况.

Following error message is displayed when I try to clone a specific repository. This happened only when cloning that repository.

remote: Enumerating objects: 991, done.
remote: Counting objects: 100% (991/991), done.
remote: Compressing objects: 100% (422/422), done.
error: index-pack died of signal 25, 60.96 MiB | 5.56 MiB/s
fatal: index-pack failed

环境:CentOS Linux 7 x86_64，具有大约1.9G的可用内存.

Environment: CentOS Linux 7 x86_64, with around 1.9G memory available.

我已经尝试过的东西，

• 在不同的机器上克隆相同的仓库；结果:成功
• 以较低的深度克隆仓库--depth=1；结果:成功

• Cloning the same repo on a different machine; Result: Successful
• Cloning the repo with a lower depth --depth=1; Result: Successful

观察

• 该存储库似乎有很多提交
• 由于克隆是在另一台计算机上进行的，因此问题应该与发生问题的计算机有关.

问题:

1. index-pack died of signal 25是什么意思?在哪里可以找到它的文档?这与Git本身或OS有关吗?
2. 我该如何解决?

1. What does index-pack died of signal 25 mean? Where can I find documentation for it? Is that related to Git itself or OS?
2. How can I solve it?

我已经搜索了类似的问题，这些问题本来会是index-pack died of signal 25，但找不到解决方案.

I've searched for similar questions which would have had index-pack died of signal 25 but couldn't find a solution.

推荐答案

根据 man 2 setrlimit 这样说:

According to man 7 signal, signal 25 is SIGXFSZ, which means "File size limit exceeded". man 2 setrlimit says this:

       RLIMIT_FSIZE
              This is the maximum size in bytes of files that the process
              may create.  Attempts to extend a file beyond this limit
              result in delivery of a SIGXFSZ signal.  By default, this sig‐
              nal terminates a process, but a process can catch this signal
              instead, in which case the relevant system call (e.g.,
              write(2), truncate(2)) fails with the error EFBIG.

您可以使用ulimit命令查看并可能更改此限制.

You can use the ulimit command to see and possibly change what this limit is.

这篇关于Git克隆:索引包因信号25死亡的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！