From: Matt Howard <mhoward@sigins.com>
To: "Miguel González Castaños" <mgc@tid.es>
Cc: linux-admin@vger.kernel.org
Subject: Re: RAID 1
Date: Fri, 14 May 2004 09:56:13 -0500 [thread overview]
Message-ID: <200405140956.13423.mhoward@sigins.com> (raw)
In-Reply-To: <40A48272.3040101@tid.es>
On Friday 14 May 2004 03:25 am, you wrote:
> Hello,
>
> I didnt know about this mdadm tool instead of using raidtools. I
> already have a production system using raidtools. Can I just remove
> raidtools and install mdadm instead with no harm in my system? I
> would like to receive an email in the case the raid state changes...
>
> Thanks in advance and sorry for my english
>
> Miguel
>
They'll even work fine together. They're both different takes on
managing the md system -- raidtools being many separate tools, mdadm
being one single tool. They both use the same system calls to manage
the raid (but different config files!). If you simply install mdadm,
you don't necessarily have to use it for *all* raid management; I add
it to Slackware boxes simply for the monitoring. Getting monitoring
for all arrays is as simple as adding these two lines to your rc.local
(or equivalent boot script):
echo "Enabling RAID Monitor."
/sbin/mdadm -F --scan -m foo@barco.net -f
--
Matt Howard <mhoward@sigins.com> 317-259-6472
Technical Services - Superior Insurance
next prev parent reply other threads:[~2004-05-14 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 18:28 RAID 1 Dean Carrera
2004-05-13 18:50 ` Marshall Lake
2004-05-13 19:05 ` Matt Howard
[not found] ` <40A48272.3040101@tid.es>
2004-05-14 14:56 ` Matt Howard [this message]
2004-05-14 9:02 ` Pau Montero Pares
2004-05-17 6:53 ` Luca Ferrari
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=200405140956.13423.mhoward@sigins.com \
--to=mhoward@sigins.com \
--cc=linux-admin@vger.kernel.org \
--cc=mgc@tid.es \
/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).