From: Calvin Walton <calvin.walton@kepstin.ca>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Javier Marcet <jmarcet@gmail.com>,
Linux Ext4 Mailing List <linux-ext4@vger.kernel.org>
Subject: Re: Far too long mount time
Date: Thu, 16 Aug 2012 10:16:48 -0400 [thread overview]
Message-ID: <1345126608.22142.59.camel@cwalton-XPS-8300> (raw)
In-Reply-To: <0F24AF1B-39C9-4300-862B-B9E84A21E34C@dilger.ca>
On Thu, 2012-08-16 at 03:09 -0600, Andreas Dilger wrote:
> On 2012-08-16, at 1:54 AM, Javier Marcet wrote:
> > I'm in the process of setting up a new software raid with four 3TB disks.
> > So far I'm doing the tests using also bcache on a 60GB partition on a 120GB
> > SSD. Everything is protected by a UPS.
> >
> > On the software side: self compiled kernel 3.5.1 and util-linux 2.20.1
> >
> > Thus far, ext4 is doing really really well but for one thing, the mount
> > time. At the moment I'm testing a RAID5 which makes the partition 8.2TB.
> >
> > ext4 takes:
> > $ time mount /mnt/raid
> > 0.00s user 79.49s system 92% cpu 1:26.25 total
> It is a bit strange that _mounting_ uses 92% CPU. Hmm, there was a bug
> reported for 3.5.1, see "Re: Upgraded from 3.4 to 3.5.1 kernel: machine
> does not boot", and reverting the patch with git commit hash
> "8aeb00ff85ad25453765dd339b408c0087db1527" resolved the problem. This
> slowdown was only seen with larger devices.
I've been seeing this as well, the symptom being the boot time on my
computer going from <5s to ~20s while my 6TB ext4 filesystem mounts.
I'll try reverting this patch; hopefully that helps.
Is there any fix for this issue queued up for an upcoming stable
release? It still reverts cleanly on 3.5.2.
--
Calvin Walton <calvin.walton@kepstin.ca>
next prev parent reply other threads:[~2012-08-16 14:16 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 [this message]
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
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=1345126608.22142.59.camel@cwalton-XPS-8300 \
--to=calvin.walton@kepstin.ca \
--cc=adilger@dilger.ca \
--cc=jmarcet@gmail.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