Bug report: Corrupt pack file after committing a large file (>4 GB?)
- From
- Yu-Hsuan Chen <davidchen9568@gmail.com>
- Date
- May 26, 2017, 05:51 UTC
- Message-ID
- <CACX31FFFk1aSn+X9VO6PkCofXPE1fjB6pugLcm+srjXFDJkmyg@mail.gmail.com>
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