linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert L Mathews <lists@tigertech.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID 1 failure on single disk causes disk subsystem to lock up
Date: Fri, 04 Apr 2008 12:11:42 -0700	[thread overview]
Message-ID: <47F67D6E.9040802@tigertech.com> (raw)
In-Reply-To: <18421.17821.6915.929392@tree.ty.sabi.co.uk>

Peter Grandi wrote:

> But have you checked whether the two ports use shared circuitry
> and in effect the two ports are on the same channel?

I've not been able to find such information at the level of detail which 
would explain whether I should expect this to fail, unfortunately (and I 
have searched).


> Because my
> impression and that of another poster is that your drives are
> sharing the same transfer logic, as if two IDE drives on the
> same ribbon.
 > ...
> For example this guy noticed the exact same problem you are
> seeing with a slightly different (one drive going offline)
> cause:

If that's the same thing, though, it doesn't seem to be a literal "the 
hardware can't handle this" issue, because the poster mentioned that the 
same test worked when running Windows instead of Linux on the same box.

It does sound like perhaps the kernel version I was using just doesn't 
quite handle this situation, and that newer versions of the kernel have 
a rewritten version of the applicable code that could conceivably make a 
difference. If (when) a disk hardware failure happens on one of these 
machines again, I'll report if anything different happens with newer 
kernels.

Thanks again!

-- 
Robert L Mathews

  "In the beginning, the universe was created. This has made a lot of
   people very angry and has been widely regarded as a bad move."
                                                    -- Douglas Adams

  reply	other threads:[~2008-04-04 19:11 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 [this message]
2008-04-02 17:43 ` Bill Davidsen
2008-04-02 18:42   ` Robert L Mathews

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=47F67D6E.9040802@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).