From: "Denis Bueno" <dbueno@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Recovering from repository corruption
Date: Tue, 10 Jun 2008 17:22:49 -0400 [thread overview]
Message-ID: <6dbd4d000806101422j39709906x1b4b03b82b504e62@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806101403080.3101@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Tue, Jun 10, 2008 at 17:09, Linus Torvalds
<torvalds@linux-foundation.org> 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 #2: 0bd6e82267b71dd2ca7043ea3f61dbbca16109 --]
[-- Type: application/octet-stream, Size: 2145 bytes --]
[-- Attachment #3: 0be2816d5eea5ae2b40990235e2225c1715927 --]
[-- Type: application/octet-stream, Size: 2110 bytes --]
next prev parent reply other threads:[~2008-06-10 21:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:26 Recovering from repository corruption Denis Bueno
2008-06-10 17:55 ` Jakub Narebski
2008-06-10 19:38 ` Denis Bueno
2008-06-10 19:59 ` Jakub Narebski
2008-06-10 20:03 ` Denis Bueno
2008-06-10 20:14 ` Jakub Narebski
2008-06-10 20:35 ` Denis Bueno
2008-06-10 20:23 ` Linus Torvalds
2008-06-10 20:28 ` Denis Bueno
2008-06-10 21:09 ` Linus Torvalds
2008-06-10 21:22 ` Denis Bueno [this message]
2008-06-10 21:48 ` Linus Torvalds
2008-06-10 22:09 ` Denis Bueno
2008-06-10 22:25 ` Tarmigan
2008-06-10 22:41 ` Denis Bueno
2008-06-10 22:45 ` Linus Torvalds
2008-06-10 23:00 ` Linus Torvalds
2008-06-11 0:43 ` Nicolas Pitre
2008-06-11 1:39 ` Linus Torvalds
2008-06-11 1:47 ` Nicolas Pitre
2008-06-10 21:27 ` Denis Bueno
2008-06-10 22:52 ` Junio C Hamano
2008-06-11 23:21 ` To graft or not to graft... (Re: Recovering from repository corruption) Stephen R. van den Berg
2008-06-11 23:34 ` Jakub Narebski
2008-06-11 23:39 ` Linus Torvalds
2008-06-12 7:14 ` Johan Herland
2008-06-12 7:47 ` Jeff King
2008-06-12 10:21 ` Johan Herland
2008-06-12 12:20 ` Stephen R. van den Berg
2008-06-10 19:40 ` Recovering from repository corruption Nicolas Pitre
2008-06-10 19:42 ` Denis Bueno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6dbd4d000806101422j39709906x1b4b03b82b504e62@mail.gmail.com \
--to=dbueno@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).