Re: Bug report: Corrupt pack file after committing a large file (>4 GB?)

From: Torsten Bögershausen <tboegi@web.de>
Date: May 26, 2017, 06:46 UTC
Message-ID: <580a63cd-890a-9c59-9cef-a08a059c2af2@web.de>
In-Reply-To: <CACX31FFFk1aSn+X9VO6PkCofXPE1fjB6pugLcm+srjXFDJkmyg@mail.gmail.com>

On 2017-05-26 07:51, Yu-Hsuan Chen wrote:

Show 20 quoted lines

> Dear maintainer,
> 
> There is a bug where committing a large file corrupts the pack file in
> Windows. Steps to recreate are:
> 
> 1. git init
> 2. stage and commit a file larger than 4 GB (not entirely sure about this size)
> 3. git checkout -f
> 
> The file checked out is much smaller than the original file size.
> 
> This behavior is surprising. If git does not support large files, I
> would at least expect an error message when staging or committing. I
> have post a question on StackOverflow regrading this issue, and has
> been confirmed by another user. (question id: 44022897)
> 
> Best regards,
> 
> David Chen
>

Issues for Git for Windows should, in general, be reported here: https://github.com/git-for-windows/git/

After 2 seconds of searching, we can find that the 4Gb problem has already been reported: https://github.com/git-for-windows/git/issues/1063

And, to my knowledge, it has not been fixed, since it is a lot of effort to replace the "long" (or unsigned long) in the Git code base with a better data type.

In other words, thanks for reminding us, more help is needed.