blocks|key|1065717|text|还有另一种可能性，即使很遥远。这将是一个非常大的文件(例如3+gb或更大)，简单地说，git无法处理它。我们发现尝试在包含大量文件的结构中创建存储库时出现错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1065718|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There is another possibility, even if remote. That would be a really big file (e.g 3 or more gb) putting it simply, git is unable to handle it. We found that error trying to create a repository in a structure with huge files

blocks|key|1065758|text|如果您尝试git+svn+clone或git+svn在btrfs文件系统上获取存储库，则可能会发生这种情况，这可能与竞争条件或btrfs+cow特性中的原子性有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1065759|示例：|1065760|git+svn+--authors-file=authors.map+clone+http://svn.example.com/svn/repo+repo|code-block|syntax|javascript|1065761|或|1065762|cd+repo;+git+svn+--authors-file=../authors.map+fetch|1065763|我找到了一个解决方法，通过设置不带写入时复制的基本工作目录：|1065764|chattr+%2BC+.|1065765|然后，您需要复制所有数据(例如：|1065766|cp+-fr+repo+repo.new;+rm+-fr+repo;+mv+-f+repo.new+repo

cp+authors.map+authors.map.new;+mv+-f+authors.map.new+authors.map|1065767|那么它就不应该失败(并且运行得更快)。|1065768|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

It can happen if you try to git svn clone or git svn fetch a repository on a btrfs filesystem, maybe something to do with race condition or atomicity inside btrfs cow feature.

Example :

<pre><code>git svn --authors-file=authors.map clone http://svn.example.com/svn/repo repo
</code></pre>

or

<pre><code>cd repo; git svn --authors-file=../authors.map fetch
</code></pre>

I found a workaround by setting you base working directory without copy-on-write :

<pre><code>chattr +C .
</code></pre>

Then you need to duplicate all your data (ex) :

<pre><code>cp -fr repo repo.new; rm -fr repo; mv -f repo.new repo

cp authors.map authors.map.new; mv -f authors.map.new authors.map
</code></pre>

Then it should not fail (and run faster).

blocks|key|1065831|text|尽管其他响应已经很好地解释了错误发生的原因，但以下是该问题的可能解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1065832|找到有问题的文件，将-v添加到git+add命令会给你一些关于有问题的文件的线索：|1065833|git+add+-Av|code-block|syntax|javascript|1065834|问题可能只是文件太大(压缩的源文件、一些sql数据文件)：将其添加到.gitignore中。|1065835|实际上，一种好的做法是定期配置.gitignore文件，以避免像下面这样的编译和压缩文件：https://gist.github.com/octocat/9257657|offset|length|1065836|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/octocat/9257657^0|0|0|0|0|19|13|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Although other responses have provided a very good explanation on why the error occurs here is a possible solution to the problem: 

Track down the problematic file, adding -v to your git add command will give you some clue about the problematic file:

<pre><code>git add -Av
</code></pre>

The problem might just be that the file is too large (a zipped source, some sql data file): add it to .gitignore

In fact a good practice is to regularly configure your .gitignore file to avoid compiled and compressed files like in: <a href="https://gist.github.com/octocat/9257657" rel="nofollow noreferrer">https://gist.github.com/octocat/9257657</a>

blocks|key|851354|text|根据我的经验，仅仅是大量添加的文件就会导致此消息。在几个步骤中提交相同的文件不是问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|851355|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my experience, just large amount of added files can cause this message. Committing the same files in several steps wasn't a problem.

Just for fun, I am trying to put around 85GB of mostly-around-6MB binary files into git. Git chugs along for a while but invariably fails about halfway through with the message "fatal: confused by unstable object source data" followed by a SHA1. Do you know why? Is there any way to fix it?

git says "fatal: confused by unstable object source data"

文件系统

只是为了好玩，我试着在git中放入大约85 git的二进制文件--大约6MB。Git进行了一段时间，但总是在中途失败，消息“致命:被不稳定的对象源数据迷惑”，后面跟着一个SHA1。你知道为什么吗？有没有办法解决这个问题？

问git说“致命的:被不稳定的对象源数据迷惑”
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git说“致命的:被不稳定的对象源数据迷惑”EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git说“致命的:被不稳定的对象源数据迷惑”
EN