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

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

[Yu-Hsuan Chen]

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

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

[Konstantin Khomoutov]

On Fri, May 26, 2017 at 01:51:34PM +0800, Yu-Hsuan Chen wrote:

> 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.

For a bug report to be at least marginally useful, please state your Git
version (run "git --version") and the version of your Windows
installation (including whether it's 32- or 64-bit install).

Please also make sure you're really using Git for Windows (that is, you
got it from [1] or [2] and not, say, from Cygwin.

The best course of actions is to download the most recent available
version from the locations mentioned above and verify the problem still
manifests itself.

1. https://git-scm.com/download/win
2. https://git-for-windows.github.io/

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

[Torsten Bögershausen]

On 2017-05-26 07:51, Yu-Hsuan Chen wrote:
> 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.