public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org
Subject: Re: RAID problems
Date: Wed, 31 Jul 2002 05:42:15 +0200	[thread overview]
Message-ID: <20020731034215.GM11129@unthought.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1020730223102.6974A-100000@gatekeeper.tmr.com>

On Tue, Jul 30, 2002 at 10:46:55PM -0400, Bill Davidsen wrote:
...
> I think you misread my comment, it was not "why doesn't the documentation
> say this" but rather "why does software RAID have this problem?"

Ok, my bad.

 - btw. I CC'ed linux-raid as this is getting a little OT for
   linux-kernel.  Let's let the thread migrate to linux-raid instead...

> I know
> this can happen in theory, but it seems that the docs imply that this
> isn't a surprise in practice. I've been running systems with SCSI RAID and

I would say it's not a surprise as such, but it's something that really
should be a very very rare occurrance.

I've seen it maybe once on a production system, having run MD on quite a
few computers for the past half decade.  And I've had a few handfulls of
people asking me about it over the years.

...
> I just surprised that the software RAID doesn't have better luck with
> this, I don't see any magic other than maybe a bus reset the firmware
> would be doing, and I'm wondering why this seems to be common with Linux.

I don't have the impression that it is common on stable hardware.  Can
anyone who runs SW RAID on a number (greater than 1) of machines comment
on this ?

However, some people run their RAID-5 arrays on the same SCSI busses as
their Zip drives, their scanners, and five other el-cheapo almost-scsi
devices, and that is just *bound* to cause this kind of mess when one of
the devices decide to lock up the bus.

You don't see this with HW raid because you don't put your $15
almost-scsi magic-foo device on your $2k HW RAID controller.

There might be other simple reasons why some HW cards don't show this
behaviour - they might simply maintain their superblocks differently
from Linux SW RAID.   I have *no* idea how current controllers do this.

> Or am I misreading the frequency with which it happens?

I hope  ;)

At least in the "stable hardware" situation.  Comments, please...

...
> Thye words are clear, I'm surprised at the behaviour. Yes, I know that's
> not your thing.

I *will* be surprised if it turns out that this is really a common
occurrence for people.   :)

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

      parent reply	other threads:[~2002-07-31  3:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 11:54 RAID problems Roy Sigurd Karlsbakk
2002-07-25 12:03 ` Neil Brown
2002-07-25 12:11 ` Jakob Oestergaard
2002-07-30 17:25   ` Bill Davidsen
2002-07-30 17:55     ` Jakob Oestergaard
2002-07-31  2:46       ` Bill Davidsen
2002-07-31  3:18         ` jeff millar
2002-07-31  3:32           ` Neil Brown
2002-07-31 14:54             ` Bill Davidsen
2002-07-31 13:35           ` Eyal Lebedinsky
2002-07-31 18:21           ` Bill Davidsen
2002-07-31  3:42         ` Jakob Oestergaard [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=20020731034215.GM11129@unthought.net \
    --to=jakob@unthought.net \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --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