From: Andargor The Wise <andargor@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: First RAID Setup
Date: Thu, 15 Dec 2005 11:09:33 -0800 (PST) [thread overview]
Message-ID: <20051215190933.16009.qmail@web54612.mail.yahoo.com> (raw)
I admit it. I'm a RAID virgin.
However, after a disastrous failure of the sole drive
I wasn't backing up, I decided to go RAID-5 under
Slack 10.2 (first time ever with RAID-5).
The config:
Asus P5GL-MX (ICH6) mobo w/1 GB RAM, 4 x SATA ports
P4 3.0G/1M
3 x WD2000JS 200.0 GB SATA drives
First, a question: the BIOS on this machine seems to
list the SATA ports as "third/fourth IDE
master/slave". Further, the documentation seems to say
that SATA 1/2 are "master" and SATA 3/4 are "slave"
(black and red connectors, respectively).
My understanding is that SATA drives are each on
separate buses. Is this because the BIOS offers a
P-ATA emulation mode for SATA and it makes it "easier"
to understand for novices to show them that way?
I ask because people have said that it is not a good
idea to have both IDE masters and slaves on the same
bus as part of a RAID-5 array. I know SATA is
different, but will using three of the SATA ports on
this mobo be OK?
Second, after reading the excellent advice in this
list, I decided that booting from RAID-5 might not be
a good idea. So this is what I've been thinking:
Each disk partitioned alike:
1 30MB
2 8GB (to allow for memory upgrades later)
5 rest_of_disk
mds:
md0 raid1 sda1 sdb1 sdc1
md1 raid1 sda2 sdb2 sdc2
md2 raid5 sda5 sdb5 sdc5
md0 /boot
md1 swap
md2 /
Does this look OK? What should the stripe and chunk
sizes be, considering I'll be going with reiserfs?
Typical usage: development machine, some DB apps with
medium load, read-only mostly, not many writes. Very
few large files (such as multimedia).
Or should I set up separate RAID-5's for /usr and /var
as well?
Lastly, can I install directly to this configuration,
or should I install on a separate disk and move things
into the array?
Andargor
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2005-12-15 19:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 19:09 Andargor The Wise [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 19:35 First RAID Setup Callahan, Tom
2005-12-15 19:44 ` Andargor The Wise
2005-12-22 14:00 ` Bill Davidsen
2005-12-15 20:02 Callahan, Tom
2005-12-15 20:22 ` Andargor The Wise
2005-12-15 20:46 ` Brad Campbell
2005-12-15 21:31 ` Tobias Hofmann
2005-12-16 1:51 ` Max Waterman
2005-12-16 8:01 ` Tobias Hofmann
2005-12-16 1:53 ` Neil Brown
2005-12-16 8:08 ` Tobias Hofmann
2005-12-19 1:02 ` Neil Brown
2005-12-19 9:03 ` Max Waterman
2005-12-16 8:42 ` Gordon Henderson
2005-12-22 14:20 ` Bill Davidsen
2005-12-22 14:24 ` Mattias Wadenstein
2005-12-15 20:37 Callahan, Tom
2005-12-17 0:00 ` Andargor The Wise
2005-12-17 2:01 ` Andargor The Wise
2005-12-18 22:08 ` Andargor The Wise
2005-12-22 14:27 ` Bill Davidsen
2005-12-22 15:00 ` Andargor The Wise
2005-12-15 21:46 Callahan, Tom
2005-12-22 17:03 Andrew Burgess
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=20051215190933.16009.qmail@web54612.mail.yahoo.com \
--to=andargor@yahoo.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).