From: Emmanuel Florac <eflorac@intellique.com>
To: Raz <raziebe@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
linux-xfs@oss.sgi.com, linux-aio@kvack.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: How to configure 36 disks ?
Date: Mon, 23 Mar 2009 15:12:57 +0100 [thread overview]
Message-ID: <20090323151257.1c7c0a8e@harpe.intellique.com> (raw)
In-Reply-To: <5d96567b0903230659t734677a3pb4fd77cccb54008b@mail.gmail.com>
Le Mon, 23 Mar 2009 15:59:47 +0200
Raz <raziebe@gmail.com> écrivait:
> 1. redundancy. fair. less likely three disks will break in a single
> raid 2. performance. bad.
> 3. modularity. yes. grows
> 4. Size 24TB
I don't understand why you'd have a bad performance here. I usually
notice a very slight difference between LVM and linux-raid raid0 in all
practical benchmarks. Did you use LVM striping capability? You may
have to adjust readahead (using blockdev --setra) on each
device /dev/dm-X and /dev/md-X) to achieve optimal performance.
--
----------------------------------------
Emmanuel Florac | Intellique
----------------------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2009-03-23 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:59 How to configure 36 disks ? Raz
2009-03-23 14:12 ` Emmanuel Florac [this message]
2009-03-23 15:35 ` Bill Davidsen
2009-03-23 16:02 ` Jon Hardcastle
2009-03-23 16:22 ` Mark Lord
2009-03-23 16:23 ` Christopher Smith
2009-03-23 16:28 ` Raz
2009-03-23 16:45 ` Greg Freemyer
2009-03-23 18:32 ` Mikael Abrahamsson
2009-03-24 19:38 ` Goswin von Brederlow
2009-03-25 12:14 ` Drew
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=20090323151257.1c7c0a8e@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=raziebe@gmail.com \
/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).