From: Andi Kleen <ak@muc.de>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
Kit Gerrits <kit@gerritsacc.nl>,
linux-scsi@vger.kernel.org
Subject: Re: Disk Errors
Date: Thu, 03 Feb 2005 09:18:21 +0100 [thread overview]
Message-ID: <m1sm4eukdu.fsf@muc.de> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458BBD5E44@otce2k01.adaptec.com> (Mark Salyzyn's message of "Wed, 2 Feb 2005 09:12:57 -0500")
"Salyzyn, Mark" <mark_salyzyn@adaptec.com> writes:
>
> If the data is of the form to permit some loss, for example video, audio
> content or an error correcting stream of data, someone can make a case
> where READ_LONG is an appropriate action to take to help fill in missing
> content.
>
> A fun thought ...
It's an interesting idea. How about adding a sysfs attribute for
the device that says "tolerate some errors". Default to off of course.
I guess a lot of people would value such an option while recovering
their disks.
-Andi
next prev parent reply other threads:[~2005-02-03 8:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 14:12 Disk Errors Salyzyn, Mark
2005-02-03 8:18 ` Andi Kleen [this message]
2005-02-15 5:56 ` Douglas Gilbert
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 18:24 Salyzyn, Mark
2005-02-02 3:55 ` Douglas Gilbert
2005-02-03 18:50 ` Bryan Henderson
2005-02-01 15:56 Cress, Andrew R
2005-02-01 12:50 Salyzyn, Mark
2005-02-01 8:53 Kit Gerrits
2005-02-01 12:43 ` Douglas Gilbert
2005-02-01 18:01 ` Bryan Henderson
2005-01-31 18:21 Disk errors Salyzyn, Mark
2005-01-31 23:41 ` Kit Gerrits
2005-01-31 23:55 ` Matt Domsch
2005-02-01 2:05 ` Guy
2005-01-31 17:11 Cress, Andrew R
[not found] <60807403EABEB443939A5A7AA8A7458BB51FD1@otce2k01.adaptec.com>
2005-01-31 16:43 ` Kit Gerrits
2005-01-31 14:46 Cress, Andrew R
2005-01-31 15:22 ` Kit Gerrits
2005-01-31 14:27 Kit Gerrits
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=m1sm4eukdu.fsf@muc.de \
--to=ak@muc.de \
--cc=hbryan@us.ibm.com \
--cc=kit@gerritsacc.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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.