From: "Dermot Paikkos" <dermot@sciencephoto.com>
To: linux-admin@vger.kernel.org
Subject: HW RAID configuration - best practise question(s)
Date: Mon, 07 Feb 2005 15:06:16 -0000 [thread overview]
Message-ID: <420783E8.6426.127A7FC@localhost> (raw)
Hi admins,
I'm about to buy a custom build server and wanted to know to
configure the RAID. This will be the first time I have configured a
RAID from scratch and I am a little un-sure about how the layout of
the system.
The server will primarily be used as a file server, uses a 3Ware SATA
8 port card and will serve about 50 users. There will initially be 4-
5 disks installed. I would like one as a hot-spare but it isn't
written in stone at this time.
My own thoughts were to keep the root file system outside of the
RAID.
This would allow me to do a complete OS re-install without effecting
the RAID. There are a couple of reasons why an OS re-install might be
desirable: I may change my distro (currently slackware) and I may
choose to try the i64 instead of i386 (AMD Opteron). This is just my
thoughts and there may be some good reasons for not configuring the
system in this way. If you have any please let me know.
What about swap? How should you configure the swap space on such a
system. Can swap space be assigned to a RAIDed file system? Should
it?
Is there anything else I should be thinking about or any documents
should read (I tried tldp.org but nothing struck me). Any thoughts?
Thanx.
Dp.
~~
Dermot Paikkos * dermot@sciencephoto.com
Network Administrator @ Science Photo Library
Phone: 0207 432 1100 * Fax: 0207 286 8668
next reply other threads:[~2005-02-07 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 15:06 Dermot Paikkos [this message]
2005-02-07 15:52 ` HW RAID configuration - best practise question(s) Jens Knoell
2005-02-07 16:04 ` Scott Taylor
2005-02-08 8:49 ` urgrue
2005-02-08 10:01 ` Dermot Paikkos
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=420783E8.6426.127A7FC@localhost \
--to=dermot@sciencephoto.com \
--cc=linux-admin@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).