From: Theodore Ts'o <tytso@mit.edu>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4: first write to large ext3 filesystem takes 96 seconds
Date: Mon, 7 Jul 2014 20:16:55 -0400 [thread overview]
Message-ID: <20140708001655.GI8254@thunk.org> (raw)
In-Reply-To: <20140707211349.GA12478@kvack.org>
On Mon, Jul 07, 2014 at 05:13:49PM -0400, Benjamin LaHaise wrote:s
> Hi folks,
>
> I've just ran into a bug with the ext4 codebase in 3.4.91 that doesn't seem
> to exist in ext3, and was wondering if anyone has encountered this before.
> I have a 7.4TB ext3 filesystem that has been filled with 1.8TB of data.
> When this filesystem is freshly mounted, the first write to the filesystem
> takes a whopping 96 seconds to complete, during which time the system is
> reading about 1000 blocks per second. Subsequent writes are much quicker.
> The problem seems to be that ext4 is loading all of the bitmaps on the
> filesystem before the first write proceeds. The backtrace looks roughly as
> follows:
So the issue is that ext3 will just allocate the first free block it
can find, even if it is a single free block in block group #1001,
followed by a single free block in block group #2002. Ext4 tries a
harder to find contiguous blocks.
If you are using an ext3 file system format, the block allocation
bitmaps are scattered across the entire file system, so we end up
doing a lot random 4k seeks.
We can try to be a bit smarter about how we try to search the file
system for free blocks.
Out of curiosity, can you send me a copy of the contents of:
/proc/fs/ext4/dm-XX/mb_groups
Thanks!!
- Ted
next prev parent reply other threads:[~2014-07-08 0:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 21:13 ext4: first write to large ext3 filesystem takes 96 seconds Benjamin LaHaise
2014-07-08 0:16 ` Theodore Ts'o [this message]
2014-07-08 1:35 ` Benjamin LaHaise
2014-07-08 3:54 ` Theodore Ts'o
2014-07-08 14:53 ` Benjamin LaHaise
2014-07-08 5:11 ` Andreas Dilger
2014-07-30 14:49 ` Benjamin LaHaise
2014-07-31 13:03 ` Theodore Ts'o
2014-07-31 14:04 ` Benjamin LaHaise
2014-07-31 15:27 ` Theodore Ts'o
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=20140708001655.GI8254@thunk.org \
--to=tytso@mit.edu \
--cc=bcrl@kvack.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.