From: Eric Sandeen <sandeen@redhat.com>
To: Karsten Weiss <K.Weiss@science-computing.de>
Cc: Dmitry Monakhov <dmonakhov@openvz.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Bad ext4 sync performance on 16 TB GPT partition
Date: Fri, 12 Mar 2010 09:20:39 -0600 [thread overview]
Message-ID: <4B9A5BC7.3030508@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1003121227040.13248@wong.science-computing.de>
Karsten Weiss wrote:
> Hi Eric!
>
> On Mon, 1 Mar 2010, Eric Sandeen wrote:
>
>>> Sorry for the delay, here's the (good) 2.6.32 result:
>>>
>>> # /usr/bin/time bash -c "dd if=/dev/zero of=/mnt/large/10GB bs=1M count=10000 && sync"
>>> 10000+0 records in
>>> 10000+0 records out
>>> 10485760000 bytes (10 GB) copied, 46.3369 seconds, 226 MB/s
>>> 0.00user 14.17system 0:59.53elapsed 23%CPU (0avgtext+0avgdata 6224maxresident)k
>>> 0inputs+0outputs (0major+1045minor)pagefaults 0swaps
>>>
>>> To summarize:
>>>
>>> Bad: 2.6.18-164.el5 (CentOS)
>>> Bad: 2.6.18-164.11.1el5 (CentOS)
>>> Bad: 2.6.18-190.el5 (RH)
>>> Good: 2.6.32
>>> Good: 2.6.33
>
> In the meantime I've also reproduced the problem on another machine with a
> Red Hat 5.5 Beta (x86_64) installation and decided to open a bug on RH's
> bugzilla:
>
> Bad ext4 sync performance on 16 TB GPT partition
> https://bugzilla.redhat.com/show_bug.cgi?id=572930
Thanks, and thanks for double-checking upstream.
>> Thanks, I'll have to investigate that. I guess something may have gotten lost
>> in translation in the 2.6.32->2.6.18 backport.....
>
> Did you come up with anything I could test?
I'll look into this...
> Is anyone else able to reproduce the problem?
Since it's not an upstream problem, this issue is probably best discussed
in the RHEL bug, now.
Thanks,
-Eric
prev parent reply other threads:[~2010-03-12 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 10:18 Bad ext4 sync performance on 16 TB GPT partition Karsten Weiss
2010-02-26 11:33 ` Karsten Weiss
2010-02-26 11:46 ` Dmitry Monakhov
2010-02-26 15:47 ` Karsten Weiss
2010-02-26 17:49 ` Eric Sandeen
2010-03-01 8:57 ` Karsten Weiss
2010-03-01 16:22 ` Eric Sandeen
2010-03-12 11:37 ` Karsten Weiss
2010-03-12 15:20 ` Eric Sandeen [this message]
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=4B9A5BC7.3030508@redhat.com \
--to=sandeen@redhat.com \
--cc=K.Weiss@science-computing.de \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.