linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Andre Noll <maan@systemlinux.org>
Cc: Michael Godfrey <godfrey@isl.stanford.edu>,
	linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14830] When other IO is running sync times go to 10 to 20 minutes
Date: Thu, 28 Jan 2010 02:53:28 -0500	[thread overview]
Message-ID: <20100128075328.GG28459@thunk.org> (raw)
In-Reply-To: <20100127130625.GQ7517@skl-net.de>

On Wed, Jan 27, 2010 at 02:06:25PM +0100, Andre Noll wrote:
> On 11:19, bugzilla-daemon@bugzilla.kernel.org wrote:
> > After kill -9 of the sync run it took about 20 minutes before 
> > it died.
> 
> I was seeing similar behaviour on one of our servers, and changing
> the io scheduler to noop fixed things for me. So it seems to be an
> issue with cfq which is somehow triggered by ext4 but not by ext3.
> 
> To change the IO scheduler, just execute
> 
> 	echo noop > /sys/block/sda/queue/scheduler
> 
> (replace sda if necessary).

Andre or Michael.  If switching away from cfq helps, that's
definitely... interesting.  Given that cfq is the default scheduler, I
definitely want to understand what might be going on here.  Are either
if you able to run blktrace so we can get a sense of what is going on
under the cfq and deadline/noop I/O schedulers?

And in both of your cases, were you using a new file system freshly
created using mke2fs -t ext4, or was this a ext2/ext3 filesystem that
was converted for use under ext4?

Thanks,

					- Ted

  parent reply	other threads:[~2010-01-28  8:35 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
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 [this message]
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=20100128075328.GG28459@thunk.org \
    --to=tytso@mit.edu \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=godfrey@isl.stanford.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=maan@systemlinux.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 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).