From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: GeneralNMX <generalmx@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Properly setting up partitions and verbose boot
Date: Mon, 26 Jan 2009 02:20:13 +0100 [thread overview]
Message-ID: <20090126012013.GB28271@rap.rap.dk> (raw)
In-Reply-To: <001401c97f08$91205150$b360f3f0$@com>
On Sun, Jan 25, 2009 at 11:18:31AM -0500, GeneralNMX wrote:
>
> Currently I have a very stupid setup on my home server (not a production
> machine). I have four hard drives with three different types of RAID
> (1,5,10) on them setup through mdadm. I've been using this for a while and,
> as you can guess, I/O Wait is a big issue for me, especially when moving
> from different RAID types. I ordered four new hard drives to setup a proper
> RAID10 by itself and I'm scrapping the RAID1, instead just consolidating /
> into the RAID10. /boot gets its own tiny IDE HDD in a hotswap bay. The RAID5
> will consume the 4 old hard drives.
Why do you think it is stupid?
I have a similar setup described in a howto at:
http://linux-raid.osdl.org/index.php/Preventing_against_a_failing_disk
How big is the iowait issue for you?
What are the performance of your raids?
> With my stupid setup, each partition gets its own /dev/mdX device. This is
> the only way I know how to do it. On the RAID10, I will need at least two
> partitions: / and swap. This means it cannot simply partition the entire
> disk Would this cause sub-optimal performance? Is there a way to make an
> underlying single RAID10 partition and place the file partitions on top?
I dont think it would be suboptimal. But try it out, both solutions and
see for yourself and report to the list your findings!).
I don't think having two raid10.f2 partitions, one for / and one for
swap, will be suboptimal, given the number of drives involved. Each
raid will do its best for the IO, and the difference between haveing it
all on one raid, vs having it on two raids, would to be be
insignificant. Where should the extra overhead come from? I even think
the elevator algorithm would be the same, as the elevator is per drive
(As far as I understand it).
do you think that the different raid types make performance problems?
I think you can partition a MD device into more partitions.
I have not tried it out for production, though and I dont know how it
performs.
I am in the process of setting up two quad-core machines with 8 GB ram
for use as virtual servers, and intend to have rai10,f2 in the buttom of
the dom0, and then let the different virtual machines have partitions on
the raid10 array. Is this recommendable? I was thinkin of problems of
both dom0 and domu doing IO, and thus copying io buffers twice.
Best regards
keld
next prev parent reply other threads:[~2009-01-26 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 16:18 Properly setting up partitions and verbose boot GeneralNMX
2009-01-26 1:20 ` Keld Jørn Simonsen [this message]
2009-01-26 16:06 ` GeneralNMX
2009-01-27 4:26 ` 'Keld Jørn Simonsen'
2009-01-28 18:13 ` 'Keld Jørn Simonsen'
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=20090126012013.GB28271@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=generalmx@gmail.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).