From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Performance question
Date: Wed, 21 Jan 2009 01:15:03 +0100 [thread overview]
Message-ID: <20090121001503.GA26587@rap.rap.dk> (raw)
In-Reply-To: <20090119181253.GA4290@lazy.lzy>
On Mon, Jan 19, 2009 at 07:12:53PM +0100, Piergiorgio Sartor wrote:
> Hi,
>
> thanks for the answer, that was exactly what I
> was looking for.
Good!
> Some feedback for you.
> About the performance & benchmarking I've nothing
> special to say.
> About the setup of two disks, I've some questions,
> in no particular order.
>
> The creation of "mdadm.conf" is done by:
>
> mdadm --detail --scan
>
> Somewhere else I found:
>
> mdadm --examine --scan
>
> The two produce different results and the Fedora
> installer seems to use the second one.
>
> Which one is really correct? Can we use one or the
> other interchangeably?
--detail looks at the running arrays, while --examine most
likely (depending on mdadm.conf) looks at all partitions
on the system.
Given that the arrays are just created in the installation process, and
the active running arrays are most likely the ones you want your system
to know of, I think --detail is the better. --examine does on two of my
systems generate info that are in conflict and not suitable for a
mdadm.conf file, such as two /dev/md1 with different UUIDs.
> Second question.
> The wiki page does not mention anything about
> metadata types.
> While it is clear that /boot must have the RAID
> header at the end, it is not clear if the RAID-10,f2
> could or should have the metadata at the beginning.
> In this respect, it would be nice also to have some
> clarification about the reccommended metadata version,
> i.e. is it better 0.90 or 1.x? Why?
To me it does not matter that much, except for the booting device.
Each partition in the booting device must look like a normal (ext3)
partition, as grub and lilo does not know of raids, and just treats
a booting partition as a standalone partition. So here you should use
0.90 metadata, which is put at the end of the array.
For other arrays I think one important choice is if you have an array
greater than 2 TiB to not use 0.90 metadata, as this has a limit of 2
TiB.
> One note. Maybe it could be worth to mention that
> further "partitioning" could be done with LVM on top
> of the RAID, so only 3 md devices will be needed.
yes, I have been looking into that. Maybe I will add some words on this.
> Hope this helps.
yes, thanks for your feedback!
best regards
keld
next prev parent reply other threads:[~2009-01-21 0:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 17:18 Performance question Piergiorgio Sartor
2009-01-17 18:37 ` Bill Davidsen
2009-01-17 22:08 ` Keld Jørn Simonsen
2009-01-19 18:12 ` Piergiorgio Sartor
2009-01-21 0:15 ` Keld Jørn Simonsen [this message]
2009-01-21 1:05 ` Richard Scobie
2009-01-21 19:14 ` Piergiorgio Sartor
2009-01-21 20:15 ` Keld Jørn Simonsen
2009-01-21 20:26 ` Piergiorgio Sartor
-- strict thread matches above, loose matches on Subject: below --
2009-01-17 18:11 David Lethe
2009-01-17 18:20 ` Piergiorgio Sartor
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=20090121001503.GA26587@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
/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).