Hi, If a loose object is empty, "git fsck" reports it as corrupt (which is good), but with the following error message: $ git fsck Checking object directories: 100% (256/256), done. fatal: failed to read object c1738f6288c9e5d5e58da00ced34d284ae93976c: Invalid argument $ cat .git/objects/c1/738f6288c9e5d5e58da00ced34d284ae93976c $ ls -l .git/objects/c1/738f6288c9e5d5e58da00ced34d284ae93976c -r--r--r-- 1 moy synchron 0 Jan 20 16:20 .git/objects/c1/738f6288c9e5d5e58da00ced34d284ae93976c "Invalid argument" is really not the error message one would expect. Before that, git used to say: fatal: loose object c1738f6288c9e5d5e58da00ced34d284ae93976c (stored in .git/objects/c1/738f6288c9e5d5e58da00ced34d28 4ae93976c) is corrupt Which was far better. This bisects back to 3ba7a065527a (A loose object is not corrupt if it cannot be read due to EMFILE), which essentially boils down to: --- a/sha1_file.c +++ b/sha1_file.c @@ -2090,16 +2090,21 @@ void *read_sha1_file_repl(const unsigned char *sha1, const unsigned char **replacement) [...] + errno = 0; + data = read_object(repl, type, size); if (data) { if (replacement) *replacement = repl; return data; } + if (errno != ENOENT) + die_errno("failed to read object %s", sha1_to_hex(sha1)); + Thanks, -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html