From: Robert L Mathews <lists@tigertech.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 1 failure on single disk causes disk subsystem to lock up
Date: Wed, 02 Apr 2008 11:42:25 -0700 [thread overview]
Message-ID: <47F3D391.50003@tigertech.com> (raw)
In-Reply-To: <47F3C5B0.2040206@tmr.com>
Bill Davidsen wrote:
> If you look at the change logs for versions between 2.6.8 and 2.6.24 you
> will see a lot of improvements in disk error handling. The kernel you
> are running is probably incapable of handling the particular failure you
> are getting, at least for values of "handle" which include "cleanly
> report failure back to the md layer."
Thanks -- yep, that makes sense. I appreciate the advice. I'll see what
happens now that we're using 2.6.18 instead of 2.6.8.
> Unless you have some very good
> reason for upgrading to another old kernel
> ...
> Security backports seem to be aimed at intrusion prevention and not
> data security in this case.
Yep. We have to stick to Debian versions offering security support,
unfortunately, for security reasons. The machines are Web servers that
allow strangers (aka customers) shell access, and intrusion prevention
is paramount :-( In a few months, the next version of Debian will
allow us to upgrade to 2.6.24.
Again, thanks for the comments, everyone; much appreciated.
--
Robert L Mathews
prev parent reply other threads:[~2008-04-02 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 23:22 RAID 1 failure on single disk causes disk subsystem to lock up Robert L Mathews
2008-03-31 10:01 ` Justin Piszcz
2008-03-31 17:30 ` Robert L Mathews
2008-03-31 19:12 ` Justin Piszcz
[not found] ` <47F0281F.1070404@harddata.com>
2008-03-31 17:27 ` Robert L Mathews
2008-03-31 19:54 ` Peter Grandi
2008-04-01 19:33 ` Richard Scobie
2008-04-02 18:33 ` Robert L Mathews
2008-04-03 21:01 ` Peter Grandi
2008-04-04 19:11 ` Robert L Mathews
2008-04-02 17:43 ` Bill Davidsen
2008-04-02 18:42 ` Robert L Mathews [this message]
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=47F3D391.50003@tigertech.com \
--to=lists@tigertech.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).