linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Steudten <alpha@steudten.com>
To: Hermann Himmelbauer <dusty@strike.wu-wien.ac.at>,
	linux-raid@vger.kernel.org
Subject: Re: swap on raid 1
Date: Tue, 14 Oct 2003 16:30:54 +0200	[thread overview]
Message-ID: <3F8C089E.3040205@steudten.com> (raw)
In-Reply-To: <200310141536.30248.dusty@strike.wu-wien.ac.at>

USB, SCSI, PATA, SATA or whatever, this are buses, and only one device
keeps a line down or high from this bus, every device can´t work correct
any more.
So to be fault resistence, you need two controllers with only one device
connected to it, or two controllers connected to every one device
(dual channel). So if one controller fails, the device can talk over
the other one. And if the device fails, you can HOPE that it won´t
keep the two (SCSI) interfaces in a invalid state.
On the other hand with two controllers, you have only one systemboard or cpu
which can fail too.
With raid you can catch device errors like, bad-blocks, disk error, but
not that the device/ disk keeps the bus.. (HW Error in the interface circuit).

Tom

Hermann Himmelbauer wrote:

> 
> Anyway - what exactly happens when a PATA harddisk dies? Will this only lead 
> to logentries in the syslog, or will this crash the machine due to hardware 
> reasons? Probably there would also be a difference if you would do RAID on 
> the same channel (e.g. hda, hdb) as a mulfunction of one device could jam the 
> whole IDE channel.
> 
> The same thing can apply to SCSI, too - I once experienced this myself when a 
> fautly SCSI-CDROM jammed the whole SCSI-bus and crashed my machine.
> 
> I hope that SATA will be a lot less critical, it should support hotplugging 
> (at least with SATA 1.1, it's a pity that it's not supported with 1.0 right 
> away) and there is only one device per channel.
>

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2003-10-14 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 11:34 swap on raid 1 skopel
2003-10-14 12:01 ` Gordon Henderson
2003-10-14 13:36 ` Hermann Himmelbauer
2003-10-14 14:03   ` Gordon Henderson
2003-10-14 14:30   ` Thomas Steudten [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=3F8C089E.3040205@steudten.com \
    --to=alpha@steudten.com \
    --cc=dusty@strike.wu-wien.ac.at \
    --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).