From: Brad Campbell <brad@fnarfbargle.com>
To: Paul van der Vlis <paul@vandervlis.nl>, linux-raid@vger.kernel.org
Subject: Re: Good hardware for mdadm
Date: Sat, 30 Aug 2014 23:56:28 +0800 [thread overview]
Message-ID: <5401F42C.7050805@fnarfbargle.com> (raw)
In-Reply-To: <lts9gt$6d3$1@ger.gmane.org>
On 30/08/14 18:37, Paul van der Vlis wrote:
> op 30-08-14 11:53, Roger Heflin schreef:
>> That means you need an external config tool (serial, ilo or IMM that
>> allows remote console access), I rarely go into the data center that
>> all of the hw I run is in, and because of the remote console access
>> can fix all but truly broken hw without having hands in the DC).
>
> That's a way to repear something what's broken. Not a more redundant
> solution I was looking for. But you are right, it helps a lot. I use
> IPMI for remote console. And on some machines a serial console.
>
You do realise that the IPMI is also not redundant and uses exactly the
same memory type that the DOM offers (which you pointed out was not
redundant).
Disks die. Anything else is a hands on fix. If you want more reliable
you go dual-redundant (possibly with a hot standby).
Regards,
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next prev parent reply other threads:[~2014-08-30 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:31 Good hardware for mdadm Paul van der Vlis
2014-08-29 20:44 ` Roberto Spadim
2014-08-29 21:47 ` Paul van der Vlis
2014-08-29 21:52 ` Adam Talbot
2014-08-30 8:25 ` Paul van der Vlis
2014-08-29 22:38 ` Roger Heflin
2014-08-30 8:35 ` Paul van der Vlis
2014-08-30 9:53 ` Roger Heflin
2014-08-30 10:37 ` Paul van der Vlis
2014-08-30 15:56 ` Brad Campbell [this message]
2014-08-30 0:44 ` Roberto Spadim
2014-08-30 8:45 ` Paul van der Vlis
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=5401F42C.7050805@fnarfbargle.com \
--to=brad@fnarfbargle.com \
--cc=linux-raid@vger.kernel.org \
--cc=paul@vandervlis.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.