From: Drew <drew.kay@gmail.com>
To: David Brown <david.brown@hesbynett.no>
Cc: linux-raid@vger.kernel.org
Subject: Re: Direct disk access on IBM Server
Date: Sun, 24 Apr 2011 05:48:36 -0700 [thread overview]
Message-ID: <BANLkTi=SRxoMjpEHeS48eJBCt3qY8CMYqQ@mail.gmail.com> (raw)
In-Reply-To: <iop4s2$cjp$1@dough.gmane.org>
Hi David,
> My goal here is to understand my options before deciding. I've had a bit of
> space between getting the machine and actually having the time to put it
> into service, so I've tested a bit and thought a bit and discussed a bit on
> this mailing list. I'll probably go for hardware raid5 - which I could have
> done in the beginning. But now I know more about why that's the sensible
> choice.
I'm going to jump in a bit late but as an owner of several of these
little beasts and say this. You have a skookum RAID card on there so
use it. :) I'd also *strongly* recommend you jump for the BBU
(Battery) if you haven't already.
This hasn't been mentioned as a consideration but one more point of
going in favor with the HW RAID is this: You're away on vacation and a
drive dies. Your backup admin notices and calls an IBM monkey out to
replace the drive. He goes, finds the failed drive indicated by the
little warning light, and replaces it. You get back to find a zero
dollar service order on your desk. :-)
I don't know about your shop but that's how it'd play out in mine.
mdadm is a great product no doubt, but to work effectively with it
everyone involved has to understand it. If you're a one man show like
I am, with vendors who don't really touch linux (not as much money in
it vs M$), making your linux systems as foolproof as possible is
important, especially when the bosses are somewhat biased against it.
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
"This started out as a hobby and spun horribly out of control."
-Unknown
--
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
next prev parent reply other threads:[~2011-04-24 12:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 13:21 Direct disk access on IBM Server David Brown
2011-04-19 13:25 ` Mathias Burén
2011-04-19 14:04 ` David Brown
2011-04-19 14:07 ` Mathias Burén
2011-04-19 15:12 ` David Brown
2011-04-19 15:41 ` Mathias Burén
2011-04-20 8:08 ` David Brown
2011-04-19 20:08 ` Stan Hoeppner
2011-04-20 11:24 ` David Brown
2011-04-20 11:40 ` Rudy Zijlstra
2011-04-20 12:21 ` David Brown
2011-04-21 6:24 ` Stan Hoeppner
2011-04-21 11:36 ` David Brown
2011-04-23 14:05 ` Majed B.
2011-04-23 14:42 ` David Brown
2011-04-24 12:48 ` Drew [this message]
2011-04-24 20:00 ` David Brown
2011-04-24 20:25 ` Rudy Zijlstra
2011-04-25 9:42 ` David Brown
2011-04-21 3:50 ` Ryan Wagoner
2011-04-21 11:00 ` David Brown
2011-04-21 4:10 ` Stan Hoeppner
2011-04-21 11:19 ` David Brown
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='BANLkTi=SRxoMjpEHeS48eJBCt3qY8CMYqQ@mail.gmail.com' \
--to=drew.kay@gmail.com \
--cc=david.brown@hesbynett.no \
--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).