From: Douglas Gilbert <dougg@torque.net>
To: Laurie Costello <lmcostello@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: non-zero result with NO_SENSE
Date: Thu, 02 Nov 2006 11:10:16 -0500 [thread overview]
Message-ID: <454A1868.9080507@torque.net> (raw)
In-Reply-To: <20061102142859.93227.qmail@web31007.mail.mud.yahoo.com>
Laurie Costello wrote:
> I'm researching a problem with data corruption on linux 2.6.9.
>
> I'm seeing results of scsi_print_sense() in the system log, which brought me
>
> to this chunk of code. Is it correct to process a non-zero result with
>
> NO_SENSE as if an error didn't occur or was recovered?
Laurie,
Well it isn't ideal obviously. The problem is that sd
sits between a SCSI direct access device and the SCSI
block subsystem. SCSI devices try and be helpful and
tell the application client things like: the data was
read but required 3 retries and ECC. The block layer
is only interested in errors that impact the current
IO, so sd has no slot to file these warnings in, apart
from the system log. There was some proposal about
logging such errors and warning (but where to store
the log :-) ) and disks already do a fair amount of
logging themselves.
Even more worrying are deferred errors. Something like
a cached write that at some later time gets an IO error
when the disk tries to write its cache to the media.
This should become a more interesting area as disks get
larger non-volatile caches.
There are tools such as smartmontools that can monitor
the health of disks.
Doug Gilbert
next prev parent reply other threads:[~2006-11-02 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 14:28 non-zero result with NO_SENSE Laurie Costello
2006-11-02 16:10 ` Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 16:58 Laurie Costello
2006-11-02 19:06 ` Douglas Gilbert
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=454A1868.9080507@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=lmcostello@yahoo.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.