From: Just Marc <marc@corky.net>
To: linux-kernel@vger.kernel.org
Cc: Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [PATCH 4/5] readahead: backoff on I/O error
Date: Sun, 11 Jun 2006 06:34:51 +0100 [thread overview]
Message-ID: <448BAB7B.6020002@corky.net> (raw)
Hi,
>Well, it looks like I'm the only one in this world who's drive was
>fired this way... ;) Note it's a combination of two issues: it's
>definitely a buggy firmware (or hardware) - it should not fire,
>no matter how you're hitting it from software - and the readahead+
>EIO logic. So.. well, I don't want to try another drive really,
>but it *seems* like it will eventually "recover". Not that it's
>possible still to watch a DVD with a single scratch (one unreadable
>block) anyway with current code (it will freeze and freeze and freeze
>again and again), but well, it's not really THAT critical. My drive
>is already dead, nothing worse can happen to it anyway ;)
I'm pretty sure you're not the only one, I have had my CD/DVD drive *obsessively*
try to read from a bad CD/DVD (or just a badly scrached area on the disc),
bringing the system to an unusable state and not even stopping in reasonable time
(minutes, at least), I was forced to power cycle the laptop in all of these cases.
Marc
next reply other threads:[~2006-06-11 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 5:34 Just Marc [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 8:08 [PATCH 0/5] Adaptive readahead updates 2 Wu Fengguang
2006-06-09 8:08 ` [PATCH 4/5] readahead: backoff on I/O error Wu Fengguang
2006-06-09 8:08 ` Wu Fengguang
2006-06-10 18:33 ` Ingo Oeser
2006-06-10 19:48 ` Michael Tokarev
2006-06-12 1:12 ` Wu Fengguang
2006-06-12 1:12 ` Wu Fengguang
2006-06-12 3:43 ` Andrew Morton
2006-06-12 11:06 ` Michael Tokarev
2006-06-17 6:38 ` Michael Tokarev
2006-06-17 7:00 ` Michael Tokarev
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=448BAB7B.6020002@corky.net \
--to=marc@corky.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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.