From: Brad Campbell <brad@wasp.net.au>
To: Greg Stark <gsstark@mit.edu>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Crashed Drive, libata wedges when trying to recover data
Date: Thu, 02 Sep 2004 13:05:59 +0400 [thread overview]
Message-ID: <4136E277.6000408@wasp.net.au> (raw)
In-Reply-To: <87oekpvzot.fsf@stark.xeocode.com>
Greg Stark wrote:
> Any clue what I need to do to achieve this? Is this a bug because this isn't a
> well-travelled code-path? (Dead drives not being something you can conjure up
> on demand)? Or is this indicative of more problems than just a crashed drive?
>
> This is on a stock 2.6.6 kernel tree, btw.
>
Known issue, fixed in 2.6.9-rc1. Apply this to 2.6.6 and your good to go.
Regards,
Brad
brad@srv:/usr/src$ diff -u temp/linux-2.6.8.1/drivers/scsi/libata-scsi.c
linux-2.6.8.1/drivers/scsi/libata-scsi.c
--- temp/linux-2.6.8.1/drivers/scsi/libata-scsi.c 2004-08-14 14:55:19.000000000 +0400
+++ linux-2.6.8.1/drivers/scsi/libata-scsi.c 2004-08-18 01:04:11.000000000 +0400
@@ -213,6 +213,7 @@
ap = (struct ata_port *) &host->hostdata[0];
ap->ops->eng_timeout(ap);
+ host->host_failed--;
DPRINTK("EXIT\n");
return 0;
T
next prev parent reply other threads:[~2004-09-02 9:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 8:32 Crashed Drive, libata wedges when trying to recover data Greg Stark
2004-09-02 9:05 ` Brad Campbell [this message]
2004-09-03 4:52 ` Greg Stark
2004-09-03 5:13 ` Greg Stark
2004-09-03 11:08 ` Alan Cox
2004-09-03 14:27 ` Greg Stark
2004-09-03 13:53 ` Alan Cox
2004-09-03 15:58 ` Greg Stark
2004-09-03 15:09 ` Alan Cox
2004-09-03 16:47 ` Greg Stark
2004-09-03 17:08 ` Eric Mudama
2004-09-03 17:35 ` Greg Stark
2004-09-03 17:57 ` Greg Stark
2004-09-03 19:45 ` Brad Campbell
2004-09-04 0:10 ` Eric Mudama
2004-09-03 12:51 ` Brad Campbell
2004-09-03 14:09 ` Alan Cox
2004-09-04 21:58 ` Greg Stark
2004-09-05 4:02 ` Brad Campbell
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=4136E277.6000408@wasp.net.au \
--to=brad@wasp.net.au \
--cc=gsstark@mit.edu \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.