From: Bill Davidsen <davidsen@tmr.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Expandable raid
Date: Sat, 13 Sep 2008 11:29:04 -0400 [thread overview]
Message-ID: <48CBDC40.1010505@tmr.com> (raw)
I am setting up a system with five drives. Initially two will be for the
system and three for other uses. In about 4-6 weeks the three will be
added to the original two. Thoughts on picking a raid config to make
this easy? I would like to use raid-10, but I don't see a way to grow it.
Kernel will be initially FC9 (whatever is shipping in the next few
days), but a kernel.org 2.6.27 will be going in shortly in hopes that
the changes to MTRR handling will allow a PAE kernel to use all of 8GB
memory in 32 bit mode.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next reply other threads:[~2008-09-13 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 15:29 Bill Davidsen [this message]
2008-09-14 11:16 ` Expandable raid Peter Grandi
2008-09-14 16:29 ` Bill Davidsen
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=48CBDC40.1010505@tmr.com \
--to=davidsen@tmr.com \
--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).