From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>, Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ext4@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: mdadm software raid + ext4, capped at ~350MiB/s limitation/bug?
Date: Sun, 28 Feb 2010 10:03:04 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002281000120.22822@p34.internal.lan> (raw)
In-Reply-To: <170fa0d21002280633x2ea6a281tf53996834c46d831@mail.gmail.com>
On Sun, 28 Feb 2010, Mike Snitzer wrote:
> On Sun, Feb 28, 2010 at 4:45 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
[ .. ]
>
> How did you format the ext3 and ext4 filesystems?
>
> Did you use mkfs.ext[34] -E stride and stripe-width accordingly?
> AFAIK even older versions of mkfs.xfs will probe for this info but
> older mkfs.ext[34] won't (though new versions of mkfs.ext[34] will,
> using the Linux "topology" info).
Yes and it did not make any difference:
http://lkml.org/lkml/2010/2/27/77
Incase anyone else wants to try too, you can calculate by hand, or if you
are in a hurry, I found this useful:
http://busybox.net/~aldot/mkfs_stride.html
I believe there is something fundamentally wrong with ext4 when performing
large sequential I/O when writing, esp. after Ted's comments.
Justin.
next prev parent reply other threads:[~2010-02-28 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 13:47 mdadm software raid + ext4, capped at ~350MiB/s limitation/bug? Justin Piszcz
2010-02-27 21:01 ` Neil Brown
2010-02-27 21:30 ` Justin Piszcz
2010-02-28 0:09 ` Bill Davidsen
2010-02-28 9:45 ` Justin Piszcz
2010-02-28 14:26 ` Bill Davidsen
2010-02-28 15:00 ` Justin Piszcz
2010-02-28 14:33 ` Mike Snitzer
2010-02-28 15:03 ` Justin Piszcz [this message]
2010-02-28 15:36 ` Bill Davidsen
2010-02-28 20:03 ` Justin Piszcz
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=alpine.DEB.2.00.1002281000120.22822@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=davidsen@tmr.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=snitzer@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