On Tue, Jun 10, 2008 at 17:09, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> No, almost all the interest is basically in how the whole repo ties
> together. The individual corrupt files may be interesting, though, ie from
> your original report:
>
> error: 320bd6e82267b71dd2ca7043ea3f61dbbca16109: object corrupt or missing
> error: 4d0be2816d5eea5ae2b40990235e2225c1715927: object corrupt or missing
>
> then *if* you have the files
>
> .git/objects/32/0bd6e82267b71dd2ca7043ea3f61dbbca16109
> .git/objects/4d/0be2816d5eea5ae2b40990235e2225c1715927
>
> then those two files are interesting in themselves (most likely they are
> not there at all, or are zero-sized, but if you have them, please post
> them).
They are attached, and they are not zero-sized.
> And as this was a result of a real filesystem crash, it *is* possible that
> you have something in the /lost+found directory for that filesystem. If
> so, those missing files may be found there.
I checked; no such luck.
--
Denis
Attachment:
0bd6e82267b71dd2ca7043ea3f61dbbca16109
Description: Binary data
Attachment:
0be2816d5eea5ae2b40990235e2225c1715927
Description: Binary data
