public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Knutar <jk-lkml@sci.fi>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: readahead logic and I/O errors
Date: Thu, 16 Feb 2006 13:42:27 +0300	[thread overview]
Message-ID: <43F45713.4010803@tls.msk.ru> (raw)
In-Reply-To: <200602160853.16297.jk-lkml@sci.fi>

Jan Knutar wrote:
> On Wednesday 15 February 2006 22:35, Michael Tokarev wrote:
> 
> 
>>after FIRST I/O error, linux continued trying reading-ahead,
>>discovering more and more failed blocks, as dmesg said.
> 
> Sorry for hijacking the thread, but on another note, is there
> anyway to tell linux to tell the drive to not bother retrying
> read errors? Would be perfect for streaming video from a
> CD or DVD. Usually video players have excellent error
> recovery themselves, which probably looks better on the
> screen than the movie coming to a grinding halt due to
> the retries.

It looks like exactly the same issue.  When you set readahead
for the drive to 0 (to disable it), the only retry which is
done is the one by drive itself.  Linux return I/O error
to the application right when drive tells so, and it's up
to the application to descide what to do next - abort
(like `cp' does), or continue next (or next-to-next)
sector etc.  I don't know how to control retries in
the drive (if it's at all possible).

/mjt

  reply	other threads:[~2006-02-16 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 20:35 readahead logic and I/O errors Michael Tokarev
2006-02-15 20:59 ` linux-os (Dick Johnson)
2006-02-15 22:02   ` Michael Tokarev
2006-02-15 22:51     ` Phillip Susi
2006-02-16  6:53 ` Jan Knutar
2006-02-16 10:42   ` Michael Tokarev [this message]
2006-02-20 10:57   ` Erik Mouw

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=43F45713.4010803@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jk-lkml@sci.fi \
    --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