From: "Rev. Jeffrey Paul" <sneak@datavibe.net>
To: David Rees <dbr@greenhydrant.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: experiences with 3Ware 6400 3W-6400?
Date: Fri, 27 Jun 2003 15:45:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0306271540140.6883@datavibe.net> (raw)
In-Reply-To: <3841.208.48.139.163.1056738220.squirrel@www.greenhydrant.com>
On Fri, 27 Jun 2003, David Rees wrote:
> Gordon Henderson said:
> >
> > Eg. the PC I'm currently typing this email on is 100 miles away and I
> > don't particularly want to drive to it to fix it if a disk fails...
> >
> > gordon @ unicorn: df -h /
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/md0 236M 20M 204M 9% /
> >
> > gordon @ unicorn: cat /proc/mdstat
> > ...
> > md0 : active raid1 hdc1[1] hda1[0]
> > 249856 blocks [2/2] [UU]
> > ...
>
> So what do you do when /dev/hda fails and the computer won't reboot? Have
> you managed to get it to boot off /dev/hdc when /dev/hda isn't available?
>
> Not having to worry about these sorts of things is one reason it's nice to
> have hardware RAID for at least the boot device.
Exactly. Another issue is that I want them to be able to just swap out
(not necessarily hot, but offline even) a failed drive without my
intervention.... I assume the card will just resync it? Under linux, it'd
require mucking about with mdadm or the raidtools and I want this to be a
fire-and-forget kind of system. On solid hardware on a UPS, the only
things likely to die are the processor fan, the power supply, and the
drives... all of which can be replaced with no knowledge of the raid or
software configuration.
Additionally, I didn't realize the 7xxx cards were that cheap. If i'm
just using raid 1 or possibly raid10, is it really going to make that much
of a difference?
-j
--
--------------------------------------------------------
Rev. Jeffrey Paul -datavibe- sneak@datavibe.net
aim:x736e65616b pgp:0x15FA257E phone:8777483467
70E0 B896 D5F3 8BF4 4BEE 2CCF EF2F BA28 15FA 257E
--------------------------------------------------------
next prev parent reply other threads:[~2003-06-27 19:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 20:57 experiences with 3Ware 6400 3W-6400? Rev. Jeffrey Paul
2003-06-26 21:01 ` Joshua Baker-LePain
2003-06-27 14:36 ` Mike Dresser
2003-06-28 14:00 ` 3ware 7500 performance, was: " Alex Verbitsky
2003-06-28 13:42 ` Mikael Abrahamsson
2003-06-28 15:00 ` Mike Dresser
2003-06-28 15:48 ` Re[2]: " Alex Verbitsky
2003-06-28 14:57 ` Mike Dresser
2003-06-26 22:17 ` David Rees
[not found] ` <2660.208.48.139.163.1056665831.squirrel@www.greenhydrant.c om>
2003-06-26 23:47 ` Maurice Hilarius
2003-06-27 7:06 ` David Rees
2003-06-27 13:24 ` Rev. Jeffrey Paul
2003-06-27 13:43 ` Gordon Henderson
2003-06-27 15:39 ` Lars Marowsky-Bree
[not found] ` <5.1.1.6.2.20030627094920.03e33780@mail.harddata.com>
[not found] ` <20030627155324.GS7800@marowsky-bree.de>
2003-06-27 16:12 ` Maurice Hilarius
2003-06-27 18:23 ` David Rees
2003-06-27 19:45 ` Rev. Jeffrey Paul [this message]
2003-06-28 11:40 ` Re[2]: " Alex Verbitsky
2003-06-27 20:19 ` Gordon Henderson
2003-06-27 18:21 ` David Rees
2003-06-27 10:13 ` Corey McGuire
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.55.0306271540140.6883@datavibe.net \
--to=sneak@datavibe.net \
--cc=dbr@greenhydrant.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).