From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <esandeen@redhat.com>
Cc: Calvin Walton <calvin.walton@kepstin.ca>,
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 15:57:34 -0400 [thread overview]
Message-ID: <20120816195734.GD31346@thunk.org> (raw)
In-Reply-To: <502D48B9.4000907@redhat.com>
On Thu, Aug 16, 2012 at 02:23:37PM -0500, Eric Sandeen wrote:
>
> And mkfs with bigalloc will do that, right?
Not yet.
We also need to make sure s_overhead_clusters gets updated after a
resize operation, but I wanted to get a fix for non-bigalloc file
systems out there as soon as possible.
> So when does all of the code after the short-circuit ever run?
Until we get ths rest of the code fixed up, it will needed for all
bigalloc file systems. The one saving grace is that bigalloc file
systems will have fewer block groups, so the O(n**2) won't be as bad
--- but it is something we really should fix.
- Ted
next prev parent reply other threads:[~2012-08-16 19:57 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
2012-08-16 19:23 ` Eric Sandeen
2012-08-16 19:57 ` Theodore Ts'o [this message]
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=20120816195734.GD31346@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=calvin.walton@kepstin.ca \
--cc=esandeen@redhat.com \
--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).