From: Hans-Peter Jansen <hpj@urpla.net>
To: andersen@codepoet.org
Cc: drd@homeworld.ath.cx, linux-kernel@vger.kernel.org
Subject: Re: A CD with errors (scratches etc.) blocks the whole system while reading damadged files
Date: Mon, 22 Apr 2002 00:54:39 +0200 [thread overview]
Message-ID: <20020422005439.0799e874.hpj@urpla.net> (raw)
In-Reply-To: <20020419200112.GA16209@codepoet.org>
On Fri, 19 Apr 2002 14:01:13 -0600
"Erik Andersen" <andersen@codepoet.org> wrote:
> This should help somewhat. Currently, ide-cd.c retries ERROR_MAX
> (8) times when it sees an error. But ide.c is also retrying
> ERROR_MAX times when _it_ sees an error, and does a bus reset
> after evey 4 failures. So for each bad sector, you get 64
> retries (with typical timouts of 7 seconds each) plus 16 bus
> resets per bad sector.
Thanks for investigation. BTW: Does this cover the ide-scsi case, too?
> The funny thing is though, we knew after the first read that we
> had an uncorrectable medium error. Try this patch vs 2.4.19-pre7
>
> --- linux/drivers/ide/ide-cd.c.orig Tue Apr 9 06:59:56 2002
> +++ linux/drivers/ide/ide-cd.c Tue Apr 9 07:04:59 2002
> @@ -657,6 +657,11 @@
> request or data protect error.*/
> ide_dump_status (drive, "command error", stat);
> cdrom_end_request (0, drive);
> + } else if (sense_key == MEDIUM_ERROR) {
> + /* No point in re-trying a zillion times on a bad
> + * sector... If we got here the error is not correctable */
> + ide_dump_status (drive, "media error (bad sector)", stat);
.. and some curious will want to know which sector has thrown the error
[which would save me to patch this some day myself...]
> + cdrom_end_request (0, drive);
> } else if ((err & ~ABRT_ERR) != 0) {
> /* Go to the default handler
> for other errors. */
> -Erik
>
> --
> Erik B. Andersen http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
Cheers,
Hans-Peter
next prev parent reply other threads:[~2002-04-21 22:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 13:13 Dr. Death
2002-04-19 14:14 ` Richard B. Johnson
2002-04-19 14:22 ` Kent Borg
2002-04-19 14:46 ` Richard B. Johnson
2002-04-19 14:50 ` A CD with errors (scratches etc.) blocks the whole system while reading damaged files Stephen Satchell
2002-04-19 14:28 ` A CD with errors (scratches etc.) blocks the whole system while reading damadged files Darrell Wright
2002-04-19 14:36 ` dr john halewood
2002-04-19 18:00 ` Oliver Xymoron
2002-04-23 22:34 ` Bill Davidsen
2002-04-24 12:31 ` Richard B. Johnson
2002-04-24 19:16 ` Bill Davidsen
2002-04-24 19:52 ` Richard B. Johnson
2002-04-24 22:58 ` Stephen Samuel
2002-04-25 3:33 ` Bill Davidsen
2002-04-26 4:04 ` Mike Fedyk
2002-04-26 5:42 ` Erik Andersen
2002-04-26 7:35 ` Andre Hedrick
2002-04-25 20:50 ` Pavel Machek
2002-04-28 2:18 ` Andre Hedrick
2002-04-26 15:48 ` Mike Fedyk
2002-04-29 21:46 ` Bill Davidsen
2002-05-02 3:45 ` Mike Fedyk
2002-05-02 8:26 ` Stephen Samuel
2002-05-02 8:49 ` Xavier Bestel
2002-05-02 8:43 ` Zwane Mwaikambo
2002-05-02 9:12 ` Xavier Bestel
2002-05-02 15:48 ` Mike Fedyk
2002-05-03 7:14 ` Xavier Bestel
2002-05-02 15:40 ` Mike Fedyk
2002-05-02 17:15 ` Stephen Samuel
2002-04-26 15:23 ` Stephen Samuel
2002-04-26 10:16 ` Zwane Mwaikambo
2002-04-19 20:01 ` Erik Andersen
2002-04-21 15:18 ` Denis Vlasenko
2002-04-21 22:54 ` Hans-Peter Jansen [this message]
2002-04-22 5:38 ` Andre Hedrick
2002-04-22 14:49 ` Roger Larsson
2002-04-30 21:18 Eric M
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=20020422005439.0799e874.hpj@urpla.net \
--to=hpj@urpla.net \
--cc=andersen@codepoet.org \
--cc=drd@homeworld.ath.cx \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®