{"thread":{"id":"46049","subject":"Bug report: Corrupt pack file after committing a large file (>4 GB?)","startedAt":"2017-05-26T05:51:40Z","lastAt":"2017-05-26T06:46:55Z","messageCount":3,"participants":["Yu-Hsuan Chen","Konstantin Khomoutov","Torsten Bögershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"320805","messageId":"CACX31FFFk1aSn+X9VO6PkCofXPE1fjB6pugLcm+srjXFDJkmyg@mail.gmail.com","threadId":"46049","inReplyTo":null,"subject":"Bug report: Corrupt pack file after committing a large file (>4 GB?)","fromName":"Yu-Hsuan Chen","fromEmail":"davidchen9568@gmail.com","sentAt":"2017-05-26T05:51:34Z","receivedAt":"2017-05-26T05:51:40Z","isPatch":false,"sender":{"key":"davidchen9568@gmail.com","avatar":null},"body":"Dear maintainer,\n\nThere is a bug where committing a large file corrupts the pack file in\nWindows. Steps to recreate are:\n\n1. git init\n2. stage and commit a file larger than 4 GB (not entirely sure about this size)\n3. git checkout -f\n\nThe file checked out is much smaller than the original file size.\n\nThis behavior is surprising. If git does not support large files, I\nwould at least expect an error message when staging or committing. I\nhave post a question on StackOverflow regrading this issue, and has\nbeen confirmed by another user. (question id: 44022897)\n\nBest regards,\n\nDavid Chen\n"},{"id":"320807","messageId":"20170526064344.o7kifhz5xjbdo4ob@tigra","threadId":"46049","inReplyTo":"CACX31FFFk1aSn+X9VO6PkCofXPE1fjB6pugLcm+srjXFDJkmyg@mail.gmail.com","subject":"Re: Bug report: Corrupt pack file after committing a large file (>4 GB?)","fromName":"Konstantin Khomoutov","fromEmail":"kostix+git@007spb.ru","sentAt":"2017-05-26T06:43:45Z","receivedAt":"2017-05-26T06:43:52Z","isPatch":false,"sender":{"key":"kostix+git@007spb.ru","avatar":null},"body":"On Fri, May 26, 2017 at 01:51:34PM +0800, Yu-Hsuan Chen wrote:\n\n> There is a bug where committing a large file corrupts the pack file in\n> Windows. Steps to recreate are:\n> \n> 1. git init\n> 2. stage and commit a file larger than 4 GB (not entirely sure about this size)\n> 3. git checkout -f\n> \n> The file checked out is much smaller than the original file size.\n\nFor a bug report to be at least marginally useful, please state your Git\nversion (run \"git --version\") and the version of your Windows\ninstallation (including whether it's 32- or 64-bit install).\n\nPlease also make sure you're really using Git for Windows (that is, you\ngot it from [1] or [2] and not, say, from Cygwin.\n\nThe best course of actions is to download the most recent available\nversion from the locations mentioned above and verify the problem still\nmanifests itself.\n\n1. https://git-scm.com/download/win\n2. https://git-for-windows.github.io/\n\n"},{"id":"320808","messageId":"580a63cd-890a-9c59-9cef-a08a059c2af2@web.de","threadId":"46049","inReplyTo":"CACX31FFFk1aSn+X9VO6PkCofXPE1fjB6pugLcm+srjXFDJkmyg@mail.gmail.com","subject":"Re: Bug report: Corrupt pack file after committing a large file (>4 GB?)","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2017-05-26T06:46:46Z","receivedAt":"2017-05-26T06:46:55Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On 2017-05-26 07:51, Yu-Hsuan Chen wrote:\n> Dear maintainer,\n> \n> There is a bug where committing a large file corrupts the pack file in\n> Windows. Steps to recreate are:\n> \n> 1. git init\n> 2. stage and commit a file larger than 4 GB (not entirely sure about this size)\n> 3. git checkout -f\n> \n> The file checked out is much smaller than the original file size.\n> \n> This behavior is surprising. If git does not support large files, I\n> would at least expect an error message when staging or committing. I\n> have post a question on StackOverflow regrading this issue, and has\n> been confirmed by another user. (question id: 44022897)\n> \n> Best regards,\n> \n> David Chen\n> \nIssues for Git for Windows should, in general, be reported here:\nhttps://github.com/git-for-windows/git/\n\nAfter 2 seconds of searching, we can find that the 4Gb problem\nhas already been reported:\nhttps://github.com/git-for-windows/git/issues/1063\n\nAnd, to my knowledge, it has not been fixed, since it is a\nlot of effort to replace the \"long\" (or unsigned long) in the\nGit code base with a better data type.\n\nIn other words, thanks for reminding us, more help is needed.\n\n\n\n"}]}