From: Linus Torvalds <torvalds@linux-foundation.org>
To: Misha Koshelev <mk144210@bcm.edu>
Cc: Andreas Ericsson <ae@op5.se>, git@vger.kernel.org
Subject: Re: Recover broken git index?
Date: Thu, 28 May 2009 14:20:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0905281413130.3435@localhost.localdomain> (raw)
In-Reply-To: <4A1EFBE9.7070805@bcm.edu>
On Thu, 28 May 2009, Misha Koshelev wrote:
>
> Actually it was technically a _clean_ restart on Ubuntu 8.04. I suspect
> there may have been some kind of strange hardware error though as
> computer was very sluggish and BIOS took a while to start up.
You may have had a disk that flaked out (disconnected from the SATA bus or
something). Sadly, when that happens, the messages obviously don't make it
to /var/log/messages, but you might have had them in your log when you
rebooted. Things like
ata1: device not ready (errno=-16), forcing hardreset
ata1: hard resetting port
ata1 SRST failed (errno=-19)
ata1: reset failed (errno=-19), retrying in 10 secs
...
and sometimes the problem doesn't go away until power is actually
disconnected, or a hard reset is performed.
It could be a one-time event, but it could also be a sign of something bad
going on with the disk. Since you likely don't have any messages anywhere,
it's hard to even guess what is going on. But your symptoms are consistent
with that (sluggish simply because some things try to read or write to
disk and will fail after a _loong_ timeout, and BIOS taking a while to
start up because it probably does some really fundamental reset thing to
get the controller back)..
Of course, that's just a guess.
Linus
prev parent reply other threads:[~2009-05-28 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 21:56 Recover broken git index? Misha Koshelev
2009-05-28 9:01 ` Andreas Ericsson
2009-05-28 12:43 ` Misha Koshelev
2009-05-28 18:09 ` Linus Torvalds
2009-05-28 21:02 ` Misha Koshelev
2009-05-28 21:20 ` Linus Torvalds [this message]
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=alpine.LFD.2.01.0905281413130.3435@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=mk144210@bcm.edu \
/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).