From: jbass@dmsd.com (John L. Bass)
To: andrew.r.cress@intel.com, jbass@dmsd.com, neilb@cse.unsw.edu.au
Cc: linux-raid@vger.kernel.org
Subject: RE: Robustness in the face of errors
Date: Mon, 18 Nov 2002 13:18:49 -0700 (MST) [thread overview]
Message-ID: <20021118201849.D67251A9823@dmsd.com> (raw)
Yeah, this is logic that scsi couldn't do by itself, but md can, since it
can recover the data.
Also, wouldn't we want to check (and even set) the auto-reallocation
(AWRE/ARRE) mode page bits on the drive when md loads, to let the disk do as
much as it can with remapping? Or does that belong outside of md?
Andy
There are limited spare resources in a drive, which are wasted if consumed by
"normal" transient errors. It's much better to recover/rewrite the sector inside
md, and if persistant then spare the sector at the drive level.
At Fortune Systems (largest M68K Unix mfgr in early 1980's) we tried auto sparing
on first error and it completely drove us crazy when the errors were introduced by
poor power and EMI coupling. The drives that were returned, were almost always good,
it was the system environment that triggered the majority of the errors.
I've been running software raid here on a large FC array ... and a number of relatively
normal errors have repeatedly taken the raid array off-line and potentially exposed
the data to corruption since the only recover is to "mkraid -R" and accept the data
state as it is.
John
next reply other threads:[~2002-11-18 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 20:18 John L. Bass [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 20:07 Robustness in the face of errors Cress, Andrew R
2002-11-16 9:56 John L. Bass
2002-11-16 12:08 ` Neil Brown
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=20021118201849.D67251A9823@dmsd.com \
--to=jbass@dmsd.com \
--cc=andrew.r.cress@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).