linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luigi Genoni <kernel@Expansa.sns.it>
To: Thunder from the hill <thunder@ngforever.de>
Cc: linux-kernel@vger.kernel.org, Martin Eriksson <nitrax@giron.wox.org>
Subject: Re: HPT370 RAID-1 or Software RAID-1, what's "best"?
Date: Fri, 15 Mar 2002 10:31:34 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0203151027560.24394-100000@Expansa.sns.it> (raw)
In-Reply-To: <3C90ECDF.8EBC8FD4@ngforever.de>

HPT370 IDE Raid is not really an hardware raid.
It is a software Raid, since Linux does not use tha raid implementation
that comes with the BIOS, but it uses softwareraid.


On Thu, 14 Mar 2002, Thunder from the hill wrote:

> Martin Eriksson wrote:
>
> > What is "best" on Linux 2.4.X (with any appropriate patches) ?
> >
> > HPT370 RAID-1 or Software RAID-1 ?
> >
> > And if Software RAID-1 is best of these two, where is it most stable; on an
> > i815 chipset, a VIA chipset (686B) or on a promise controller?
> >
> > I define "best" as:
> > * most stable
> > * least complex setup
> > * least hassle when something goes wrong
>
> Software RAID is just your disk configuration. But I'd recommend
> hardware raid because the rebuild after one disk crash is dog slow with
> software raid. This problem been discussed in all possible linux
> magazines...
> I prefer \x13SCSI RAID5
>
> Thunder
> --
> begin-base64 755 -
> IyEgL3Vzci9iaW4vcGVybApteSAgICAgJHNheWluZyA9CSMgVGhlIHNjcmlw
> dCBvbiB0aGUgbGVmdCBpcyB0aGUgcHJvb2YKIk5lbmEgaXN0IGVpbiIgLgkj
> IHRoYXQgaXQgaXNuJ3QgYWxsIHRoZSB3YXkgaXQgc2VlbXMKIiB2ZXJhbHRl
> dGVyICIgLgkjIHRvIGJlIChlc3BlY2lhbGx5IG5vdCB3aXRoIG1lKQoiTkRX
> LVN0YXIuXG4iICA7CiRzYXlpbmcgPX4Kcy9ORFctU3Rhci9rYW5uXAogdW5z
> IHJldHRlbi9nICA7CiRzYXlpbmcgICAgICAgPX4Kcy92ZXJhbHRldGVyL2Rp
> XAplIExpZWJlL2c7CiRzYXlpbmcgPX5zL2Vpbi8KbnVyL2c7JHNheWluZyA9
> fgpzL2lzdC9zYWd0LC9nICA7CiRzYXlpbmc9fnMvXG4vL2cKO3ByaW50Zigk
> c2F5aW5nKQo7cHJpbnRmKCJcbiIpOwo=
> ====
> Extract this and see what will happen if you execute my
> signature. Just save it to file and do a
> > uudecode $file | perl
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  parent reply	other threads:[~2002-03-15  9:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 18:33 HPT370 RAID-1 or Software RAID-1, what's "best"? Thunder from the hill
2002-03-14 18:53 ` Alan Cox
2002-03-15  9:31 ` Luigi Genoni [this message]
2002-03-15 12:59   ` Martin Eriksson
2002-03-15 14:00     ` Ulrich Wiederhold
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15 14:52 Thunder from the hill
2002-03-15 15:29 ` Alan Cox
2002-03-15 16:52 ` Luigi Genoni
2002-03-15 17:43   ` Alan Cox
2002-03-15 18:07     ` Luigi Genoni
2002-03-16  1:12     ` Mike Fedyk
2002-03-18 19:56     ` Bill Davidsen
2002-03-13 21:20 Martin Eriksson

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=Pine.LNX.4.44.0203151027560.24394-100000@Expansa.sns.it \
    --to=kernel@expansa.sns.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitrax@giron.wox.org \
    --cc=thunder@ngforever.de \
    /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).