From: Sam Vilain <sam@vilain.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] hardware raid5 and lvm "recipe"
Date: Tue, 08 Mar 2005 09:31:00 +1300 [thread overview]
Message-ID: <422CBA04.3000002@vilain.net> (raw)
In-Reply-To: <FBBA14180DBE83499AC81277324251B0113181@jaxmsx01.nemours.org>
Amir Mistric wrote:
> We are contemplating to start using RHEL v4 in our enterprise.
> Most of our servers have a hardware RAID.
> The server we are using for a RHEL 4 trial install has 4x36GB SCSI
> drives configured using RAID 5.
> Of course, we also want to use LVM.
> Can someone please suggest what would be the best �layout�/�recipe�
> considering the configuration I described?
> Using �automatically� partitioning during install RHEL suggests:
> /boot and swap outside LVM and the rest of space in LVM mounted under /
> file system.
> Is this sufficient layout for maximum flexibility? Should I create other
> logical volumes and file systems?
Seems like a good enough policy. An alternative is to have a larger
root, so that you can do LVM diagnostics without using a boot CD. But
using a standard vendor configuration means that you're going to surprise
fewer admins that come along.
> Any tips are appreciated
Here's a tip... simulate a failure and make sure that you can detect it.
If you've got pluggable disks, then quiesce the system and unplug one.
Never unplug an active disk, of course.
--
Sam Vilain, sam /\T vilain |><>T net, PGP key ID: 0x05B52F13
(include my PGP key ID in personal replies to avoid spam filtering)
next prev parent reply other threads:[~2005-03-07 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 13:56 [linux-lvm] hardware raid5 and lvm "recipe" Amir Mistric
2005-03-07 20:31 ` Sam Vilain [this message]
2005-03-07 22:50 ` [linux-lvm] Fixed. But what are PV# and Cur LV in pvdata? oliver
2005-03-08 15:08 ` [linux-lvm] hardware raid5 and lvm "recipe" Michael T. Babcock
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=422CBA04.3000002@vilain.net \
--to=sam@vilain.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.