From: Chris Lee <cslee-list@cybericom.co.uk>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Bug 14830] When other IO is running sync times go to 10 to 20 minutes
Date: Tue, 19 Jan 2010 17:24:23 +0000 [thread overview]
Message-ID: <4B55EAC7.3080004@cybericom.co.uk> (raw)
In-Reply-To: <201001182358.o0INwBkc011745@demeter.kernel.org>
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14830
>
>
>
>
>
> --- Comment #3 from Michael Godfrey <godfrey@isl.stanford.edu> 2010-01-18 23:58:09 ---
>
>> This problem prevents production use of systems using this kernel.
>>
>
>
>> evokes a question: Do you have a kernel which behaved better for you? Which
>> one?
>>
>
> Yes. RHEL5.4 does not show this problem. It is the production
> system that works in this environment.
>
> The response above is disappointing. Is sync response of 20 minutes,
> including several task timeouts to be considered "normal?"
>
>
>> If you think the time is inappropriately long, we can have a look at it
>> but for that we'd need much more details like amount and nature of data writen
>> (many small files vs a few large ones), time it takes sync to complete, speed
>> of disks for sequential IO...
>>
>
> I am sorry to have to tell you that in this environment we do not
> deal in exclusively small or large files, we actually have quite a
> few of both. When an rsync which transfers about 50GB of files of
> various sizes is running, the hung condition is continuous until the rsync
> completes. This is just a pretty typical load. You could try it
> yourself. No special sizes of files are required. I think I
> mentioned that the ext4 LVM is a RAID 50 3ware 9650SE-8LPML,
> with 8 2T drives. Its throughput for reading and writing is good
> when the system is not locked up.
>
>
Is it possible that it is something allong the lines of what is
described at this link:
http://notemagnet.blogspot.com/2008/08/linux-write-cache-mystery.html
If so a runtime adjustment might help you out.
Chris.
next prev parent reply other threads:[~2010-01-19 17:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14830-13602@http.bugzilla.kernel.org/>
2010-01-13 19:15 ` [Bug 14830] When other IO is running sync times go to 10 to 20 minutes bugzilla-daemon
2010-01-18 21:50 ` bugzilla-daemon
2010-01-18 23:58 ` bugzilla-daemon
2010-01-19 17:24 ` Chris Lee [this message]
2010-01-19 17:24 ` bugzilla-daemon
2010-01-19 19:38 ` bugzilla-daemon
2010-01-19 21:56 ` bugzilla-daemon
2010-01-25 7:38 ` bugzilla-daemon
2010-01-25 8:27 ` bugzilla-daemon
2010-01-25 11:07 ` bugzilla-daemon
2010-01-25 11:16 ` bugzilla-daemon
2010-01-25 11:19 ` bugzilla-daemon
2010-01-27 13:06 ` Andre Noll
2010-01-27 19:43 ` Andreas Dilger
2010-01-28 10:24 ` Andre Noll
2010-01-28 7:53 ` tytso
2010-01-28 10:25 ` Andre Noll
2010-01-28 9:18 ` bugzilla-daemon
2010-01-28 11:23 ` bugzilla-daemon
2010-01-28 16:22 ` bugzilla-daemon
2010-01-29 0:52 ` bugzilla-daemon
2010-01-29 6:37 ` bugzilla-daemon
2010-02-04 4:16 ` bugzilla-daemon
2010-02-15 14:28 ` bugzilla-daemon
2010-02-15 18:29 ` bugzilla-daemon
2010-03-10 6:56 ` bugzilla-daemon
2010-03-10 15:36 ` bugzilla-daemon
[not found] <bug-14830-13602@https.bugzilla.kernel.org/>
2010-04-02 5:41 ` bugzilla-daemon
2010-04-02 21:23 ` bugzilla-daemon
2010-04-06 16:47 ` bugzilla-daemon
2010-04-06 16:49 ` bugzilla-daemon
2010-04-06 16:50 ` bugzilla-daemon
2010-04-06 16:52 ` bugzilla-daemon
2010-04-06 16:55 ` bugzilla-daemon
2010-04-06 23:01 ` bugzilla-daemon
2010-04-06 23:06 ` bugzilla-daemon
2010-04-07 9:33 ` bugzilla-daemon
2010-04-07 15:10 ` bugzilla-daemon
2010-04-15 8:45 ` bugzilla-daemon
2010-04-20 2:49 ` bugzilla-daemon
2010-04-20 3:46 ` bugzilla-daemon
2010-04-29 9:31 ` bugzilla-daemon
2010-04-30 6:02 ` bugzilla-daemon
2010-05-20 2:11 ` bugzilla-daemon
2010-05-20 11:11 ` bugzilla-daemon
2010-05-20 17:53 ` bugzilla-daemon
2012-06-18 13:19 ` bugzilla-daemon
2012-06-18 13:19 ` bugzilla-daemon
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=4B55EAC7.3080004@cybericom.co.uk \
--to=cslee-list@cybericom.co.uk \
--cc=bugzilla-daemon@bugzilla.kernel.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.