From: Frank Wittig <fw@weisshuhn.de>
To: John Stoffel <john@stoffel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID design decisions
Date: Sun, 18 Dec 2005 13:43:29 +0100 [thread overview]
Message-ID: <43A55971.9070206@weisshuhn.de> (raw)
In-Reply-To: <17315.27096.325885.788363@smtp.charter.net>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Hi John,
you described exactly my favourite disk setup as I prefer since I tested
several different setups with and without LVM2.
John Stoffel wrote:
> 2. mirror my /, swap and /boot partitions for reliability
> - requires mkinitrd to work well and easily for new kernels.
> - requires I don't screw up my current setup when I try this.
I use Fedora rather than Debian but I think there're only marginal
differences in RAID/LVM-Setup.
My preferred disk setup for server systems is this:
- all disks which are part of the system raid contain a first partition
of 256MB size - these partitions build up a RAID1 which holds /boot.
- on all disks with a boot-partition a Grub is installed into MBR so
each of this disks can replace the first in case of failure
- the rest of the system disk space goes into on large LVM2 vg which
holds all system partitions and swap
- if I need extra disks for e.g. postgresql database space I set up a
second volume group which contains data partitions
- I use XFS or JFS for all partitions since these are growable without
unmounting them (i resized both partition types during high disk load
without any problems)
Greetings,
Frank
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
prev parent reply other threads:[~2005-12-18 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 1:28 RAID design decisions John Stoffel
2005-12-17 18:06 ` Ross Vandegrift
2005-12-18 12:43 ` Frank Wittig [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=43A55971.9070206@weisshuhn.de \
--to=fw@weisshuhn.de \
--cc=john@stoffel.org \
--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).