From: Andy Smith <andy@strugglers.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] raidtools/mdadm stability
Date: Thu, 2 Feb 2006 17:03:46 +0000 [thread overview]
Message-ID: <20060202170346.GV7017@strugglers.net> (raw)
In-Reply-To: <D3DC8F9206F0D24085E459720ECDF3EDC3FC34@mail-18ps.atlarge.net>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Thu, Feb 02, 2006 at 10:15:52AM -0600, Don Shesnicky wrote:
> Couple of quick questions on raidtools/mdadm if anyone cares to comment:
>
> 1. In the raid faq it states "However, if you find raidtools cumbersome
> or limited, mdadm (multiple devices admin) is an extremely useful tool
> for running RAID systems. It can be used as a replacement for the
> raidtools, or as a supplement." I want to mirror the root drives of a
> RHEL4 ES U2 system, what's the prefered method for stability -
> raidtools,
> mdadm or mdadm with raidtools.
raidtools is obsolete, so mdadm.
> 2. I take it from a previous posting I can mirror my two root drives,
> installed the MBRs and be good to go to boot off either drive, that
> the mirror is not at the bit level and does not include the MBR?
The mirror is at the block device level, e.g. if your root fs is
/dev/sda1 then that's what you mirror. So you could install an MBR
on sda and sdb for example.
> 3. Is RHEL4 ES Update2 generally stable or is there something that
> could burn us here?
I have had no issues whatsoever with LVM or mdadm in RHEL3 or 4.
Apart from LVM snapshots, of course.
--
http://strugglers.net/wiki/Xen_hosting -- A Xen VPS hosting hobby
Encrypted mail welcome - keyid 0x604DE5DB
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-02 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 16:15 [linux-lvm] raidtools/mdadm stability Don Shesnicky
2006-02-02 17:03 ` Andy Smith [this message]
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=20060202170346.GV7017@strugglers.net \
--to=andy@strugglers.net \
--cc=linux-lvm@redhat.com \
/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.