{"thread":{"id":"37798","subject":"Fatal: <hash> is corrupted can be caused by wrong permissions","startedAt":"2014-10-24T13:48:02Z","lastAt":"2014-10-25T10:17:41Z","messageCount":3,"participants":["R. David Murray","Matthieu Moy","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"251010","messageId":"20141024134802.93466250E0D@webabinitio.net","threadId":"37798","inReplyTo":null,"subject":"Fatal: <hash> is corrupted can be caused by wrong permissions","fromName":"R. David Murray","fromEmail":"rdmurray@bitdance.com","sentAt":"2014-10-24T13:48:02Z","receivedAt":"2014-10-24T13:48:02Z","isPatch":false,"sender":{"key":"rdmurray@bitdance.com","avatar":null},"body":"A quick search of your mailing list didn't turn up any good hits (not the most\nsearchable terms and gmane search doesn't seem to support phrases), so I'm\nreporting this.\n\nOn git 1.7.1 I ran into the Fatal corruption error in one of my projects.  For\nreasons that are irrelevant I was operating on the repo as user X, a member of\ngroup Z, but the files were all owned by Y:Z, with (I thought) -rw-rw---\npermissions.  After a bunch of head banging I finally figured out that the\nFatal error wasn't because the object files were corrupted, but because three\nobjects (for reasons unknown to me that are probably lost in the early history\nof the setup of this particular repo...one of the blobs was the first commit)\nwere -rw-----.  So it seems to me that the error message could be improved to\nindicate that the reason the object couldn't be used was a permission error.\nThat's  a different thing from the contents being corrupted.\n\n--David\n"},{"id":"251011","messageId":"vpqbnp1zhp7.fsf@anie.imag.fr","threadId":"37798","inReplyTo":"20141024134802.93466250E0D@webabinitio.net","subject":"Re: Fatal: <hash> is corrupted can be caused by wrong permissions","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2014-10-24T14:05:24Z","receivedAt":"2014-10-24T14:05:24Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"\"R. David Murray\" <rdmurray@bitdance.com> writes:\n\n> On git 1.7.1 I ran into the Fatal corruption error in one of my projects.  For\n> reasons that are irrelevant I was operating on the repo as user X, a member of\n> group Z, but the files were all owned by Y:Z, with (I thought) -rw-rw---\n> permissions.  After a bunch of head banging I finally figured out that the\n> Fatal error wasn't because the object files were corrupted, but because three\n> objects (for reasons unknown to me that are probably lost in the early history\n> of the setup of this particular repo...one of the blobs was the first commit)\n> were -rw-----.\n\nI can reproduce with Git 1.7.10 by doing a chmod 0 on some object files,\nbut recent Git's produce\n\nChecking object directories: 100% (256/256), done.\nfatal: failed to read object ab2e06e74d922268fbff8d219dad9eee63786947: Permission denied\n\nSo I guess this has already been fixed :-).\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"251042","messageId":"20141025101741.GA17058@peff.net","threadId":"37798","inReplyTo":"vpqbnp1zhp7.fsf@anie.imag.fr","subject":"Re: Fatal: <hash> is corrupted can be caused by wrong permissions","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2014-10-25T10:17:41Z","receivedAt":"2014-10-25T10:17:41Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Fri, Oct 24, 2014 at 04:05:24PM +0200, Matthieu Moy wrote:\n\n> I can reproduce with Git 1.7.10 by doing a chmod 0 on some object files,\n> but recent Git's produce\n> \n> Checking object directories: 100% (256/256), done.\n> fatal: failed to read object ab2e06e74d922268fbff8d219dad9eee63786947: Permission denied\n> \n> So I guess this has already been fixed :-).\n\nProbably d6c8a05 (open_sha1_file: report \"most interesting\" errno,\n2014-05-15). The example in the commit message even uses \"chmod 0\". :)\n\nIt's in v2.0.1.\n\n-Peff\n"}]}