From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14830] When other IO is running sync times go to 10 to 20 minutes
Date: Fri, 2 Apr 2010 05:41:35 GMT [thread overview]
Message-ID: <201004020541.o325fZKw007754@demeter.kernel.org> (raw)
In-Reply-To: <bug-14830-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14830
--- Comment #22 from Michael Godfrey <godfrey@isl.stanford.edu> 2010-04-02 05:41:26 ---
I tried another test with 2.6.32.10-90.fc12.x86_64. I did
not expect an improvement. But, the results were actually
a lot worse. After starting an rsync which transferred a
few 100GB through NFS, I started a sync using time sync.
This caused a number of the usual 2 minute timeout messages. But, also
it did not close until about 20 minutes after the rsync had
completed. All together it ran for several hours. By the
way it was not possible to kill the sync using kill -9.
This is clearly hopeless.
Will anything be done about this in 2.6.33 for fc13?
Will the fact that Google is going with ext4 possibly help?
Michael
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next parent reply other threads:[~2010-04-02 5:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14830-13602@https.bugzilla.kernel.org/>
2010-04-02 5:41 ` bugzilla-daemon [this message]
2010-04-02 21:23 ` [Bug 14830] When other IO is running sync times go to 10 to 20 minutes 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
[not found] <bug-14830-13602@http.bugzilla.kernel.org/>
2010-01-13 19:15 ` bugzilla-daemon
2010-01-18 21:50 ` bugzilla-daemon
2010-01-18 23:58 ` bugzilla-daemon
2010-01-19 17:24 ` Chris Lee
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
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=201004020541.o325fZKw007754@demeter.kernel.org \
--to=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.