On Tuesday, November 13, 2007 at 22:48:02 (+0100) Alex Riesen writes: >... >> >I extend the part you quoted. The file is opened here: >> >... >> >This is strange. The current git should not produce anything like >> >this (and does not, here). ... >> >> You are absolutely correct. My comrade ran this with 1.5.0.1 by >> mistake. He reran the strace with 1.5.3.5, and I have replaced >> the tarball on my server: >> >> http://www.zopyra.com/~rael/git/git-trace.tar.bz2 > >Still looks like v1.5.0.1: > > write(2, "fatal: ", 7) = 7 > write(2, "cannot pread pack file: No such "..., 49) = 49 Well, I just grepped for the above string in git-1.5.3.5: % grep 'cannot pread pack file' *.c index-pack.c: die("cannot pread pack file: %s", strerror(errno)); >I think it got worse: > >> write(3, "\360]|\204\205\317|\352\336C\342\316\206\334\326\201\211"..., 4096) = 4096 >> write(3, "\20\t\33if (cached_vias.insert(die,\227\17"..., 4096) = 4096 > >The data in packs is zlib-compressed. I don't think you should be able >to see any readable strings in them (except for "PACK" in the header). >I believe you have a data corruption now. > >Does git-fsck --all say anything about that, BTW? I'll see if we can run it... >Besides, could you try with a git compiled with NO_PREAD? I'll try this also. Bill - 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
