From: Kasra Khosoussi <kasra.mail@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: corrupted Git repository
Date: Tue, 21 Jun 2011 18:56:55 +0430 [thread overview]
Message-ID: <BANLkTi=6jt7Z3fvK++ontW=F9AJbmEr9Qg@mail.gmail.com> (raw)
In-Reply-To: <4E00A0E1.8000006@viscovery.net>
Good question! Actually I have no idea!
It was fine yesterday. I had to leave home so I just shutdown my
netbook (I just issued the command and closed the lid). Files were
open in my editor but I'm sure that there were no Git processes
running at the time. The battery was empty this morning, so my best
guess is that the halt operation was somehow failed, but I think it
can not explain the corruption.
Any idea?
-Kasra
On Tue, Jun 21, 2011 at 6:17 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Am 6/21/2011 12:10, schrieb Kasra Khosoussi:
>> Everything seems fine now
>
> But it would still be good to know how the corruption could have happened.
> Do you have any clues?
>
> Disk full?
> Ctrl-C in the middle of a git operation?
> Some cron script interference (unlikely)?
> Permission problems (unlikely)?
> Networking problems (only if the repository is on a network mount)?
> Something else?
>
> -- Hannes
>
next prev parent reply other threads:[~2011-06-21 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 6:58 corrupted Git repository Kasra Khosoussi
2011-06-21 8:19 ` Michael J Gruber
2011-06-21 9:30 ` Kasra Khosoussi
2011-06-21 9:38 ` Michael J Gruber
2011-06-21 10:10 ` Kasra Khosoussi
2011-06-21 10:39 ` Ilari Liusvaara
2011-06-21 10:40 ` Kasra Khosoussi
2011-06-21 13:47 ` Johannes Sixt
2011-06-21 14:26 ` Kasra Khosoussi [this message]
2011-06-21 14:32 ` Carlos Martín Nieto
2011-06-21 14:59 ` Kasra Khosoussi
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='BANLkTi=6jt7Z3fvK++ontW=F9AJbmEr9Qg@mail.gmail.com' \
--to=kasra.mail@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).