All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 20902] High IO wait when writing to ext4
Date: Thu, 25 Nov 2010 09:17:28 GMT	[thread overview]
Message-ID: <201011250917.oAP9HSwJ020719@demeter1.kernel.org> (raw)
In-Reply-To: <bug-20902-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=20902


Andreas Dilger <adilger.kernelbugzilla@dilger.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adilger.kernelbugzilla@dilg
                   |                            |er.ca




--- Comment #19 from Andreas Dilger <adilger.kernelbugzilla@dilger.ca>  2010-11-25 09:17:26 ---
(In reply to comment #16)
> Here's mine.  My test case is mount, sleep 5, then do 10 x 128MB writes using
> dd to the just-mounted filesystem.  The first 128MB write took over 20 seconds.
>  Unfortunately I don't have access any more to the box where it took 150
> seconds.

We've seen this problem with Lustre as well.  The root of the problem is that
the initial write to a filesystem that is fairly full causes mballoc to scan
all of the block groups looking for groups with enough space for preallocation
of an 8MB chunk.  On an 8TB filesystem with 64k groups @ 100 seeks/second this
could take up to 10 minutes to complete.

The patch from Curt committed in 8a57d9d61a6e361c7bb159dda797672c1df1a691 fixed
this for small writes at mount time, but does not help for large writes.

We are starting to look at other solutions to this problem in our bugzilla:
https://bugzilla.lustre.org/show_bug.cgi?id=24183

with a patch (currently untested) in:
https://bugzilla.lustre.org/attachment.cgi?id=32320&action=edit


Increasing the flex_bg size is likely going to reduce the severity of this
problem, by reducing the number of seeks needed to load the block bitmaps
proportional to the flex_bg factor (32 by default today).  That would change
the 8TB bitmap scan time from 10 minutes to about 20s.

Other possibilities include starting the bitmap scan at some random group
instead of always starting at group 0, storing some free extent information for
each group in the group descriptor table, or storing some information in the
superblock about which group to start allocations at.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-11-25  9:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  8:56 [Bug 20902] New: High bugzilla-daemon
2010-10-22  8:56 ` [Bug 20902] High bugzilla-daemon
2010-10-22  8:57 ` bugzilla-daemon
2010-10-22  8:57 ` bugzilla-daemon
2010-10-22  8:58 ` bugzilla-daemon
2010-10-22  8:59 ` bugzilla-daemon
2010-10-22  9:08 ` bugzilla-daemon
2010-10-22  9:18 ` [Bug 20902] High IO wait when writing to ext4 bugzilla-daemon
2010-10-22 21:52 ` bugzilla-daemon
2010-10-22 21:54 ` bugzilla-daemon
2010-10-22 21:55 ` bugzilla-daemon
2010-10-29 16:11 ` bugzilla-daemon
2010-10-29 16:23 ` bugzilla-daemon
2010-10-29 18:08 ` bugzilla-daemon
2010-10-29 21:13 ` bugzilla-daemon
2010-10-29 21:46 ` bugzilla-daemon
2010-11-04 17:59 ` bugzilla-daemon
2010-11-04 18:46 ` bugzilla-daemon
2010-11-04 18:52 ` bugzilla-daemon
2010-11-24  3:14 ` bugzilla-daemon
2010-11-24  5:13 ` bugzilla-daemon
2010-11-24 18:41 ` bugzilla-daemon
2010-11-25  9:17 ` bugzilla-daemon [this message]
2010-11-25 15:30 ` bugzilla-daemon
2013-12-10 22:21 ` 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=201011250917.oAP9HSwJ020719@demeter1.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.