From: Theodore Ts'o <tytso@mit.edu>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: Andreas Dilger <adilger@dilger.ca>,
Javier Marcet <jmarcet@gmail.com>,
Linux Ext4 Mailing List <linux-ext4@vger.kernel.org>,
jpiszcz@lucidpixels.com
Subject: Re: Far too long mount time
Date: Thu, 16 Aug 2012 14:53:37 -0400 [thread overview]
Message-ID: <20120816185337.GB31346@thunk.org> (raw)
In-Reply-To: <20120816144219.GB29410@thunk.org>
On Thu, Aug 16, 2012 at 10:42:19AM -0400, Theodore Ts'o wrote:
> On Thu, Aug 16, 2012 at 10:16:48AM -0400, Calvin Walton wrote:
> > On Thu, 2012-08-16 at 03:09 -0600, Andreas Dilger wrote:
> > Is there any fix for this issue queued up for an upcoming stable
> > release? It still reverts cleanly on 3.5.2.
>
> There isn't a fix queued up yet, but there will be one soon....
This patch should solve the problem (as an alternative to reverting
8aeb00ff85a).
- Ted
>From dc43c7a8a6c266c31aa4f0408000c4d1b9f3c787 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o <tytso@mit.edu>
Date: Thu, 16 Aug 2012 11:59:04 -0400
Subject: [PATCH] ext4: fix long mount times on very big file systems
Commit 8aeb00ff85a: "ext4: fix overhead calculation used by
ext4_statfs()" introduced a O(n**2) calculation which makes very large
file systems take forever to mount. Fix this with an optimization for
non-bigalloc file systems. (For bigalloc file systems the overhead
needs to be set in the the superblock.)
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@vger.kernel.org
---
fs/ext4/super.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 603023b..055c65b 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -3129,6 +3129,10 @@ static int count_overhead(struct super_block *sb, ext4_group_t grp,
ext4_group_t i, ngroups = ext4_get_groups_count(sb);
int s, j, count = 0;
+ if (!EXT4_HAS_RO_COMPAT_FEATURE(sb, EXT4_FEATURE_RO_COMPAT_BIGALLOC))
+ return (ext4_bg_has_super(sb, grp) + ext4_bg_num_gdb(sb, i) +
+ sbi->s_itb_per_group + 2);
+
first_block = le32_to_cpu(sbi->s_es->s_first_data_block) +
(grp * EXT4_BLOCKS_PER_GROUP(sb));
last_block = first_block + EXT4_BLOCKS_PER_GROUP(sb) - 1;
--
1.7.12.rc0.22.gcdd159b
next prev parent reply other threads:[~2012-08-16 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAnFQG_O051svcCZftDefebVEds+P1zAceteh=B18HOqmoqitg@mail.gmail.com>
2012-08-16 7:54 ` Fwd: Far too long mount time Javier Marcet
2012-08-16 9:09 ` Andreas Dilger
2012-08-16 9:18 ` Javier Marcet
2012-08-16 9:53 ` Javier Marcet
2012-08-16 14:16 ` Calvin Walton
2012-08-16 14:42 ` Theodore Ts'o
2012-08-16 18:53 ` Theodore Ts'o [this message]
2012-08-16 19:23 ` Eric Sandeen
2012-08-16 19:57 ` Theodore Ts'o
2012-08-17 13:55 ` Theodore Ts'o
2012-08-17 14:48 ` Justin Piszcz
2012-08-17 14:58 ` Theodore Ts'o
2012-08-17 15:00 ` Justin Piszcz
2012-08-17 15:13 ` Theodore Ts'o
2012-08-17 15:27 ` Theodore Ts'o
2012-08-17 19:18 ` Justin Piszcz
2012-08-17 19:44 ` Eric Sandeen
2012-08-17 15:58 ` Andreas Dilger
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=20120816185337.GB31346@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=calvin.walton@kepstin.ca \
--cc=jmarcet@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--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 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).