From: Dave Chinner <david@fromorbit.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: mount recovery taking quite long time
Date: Thu, 16 Feb 2012 11:20:36 +1100 [thread overview]
Message-ID: <20120216002036.GV14132@dastard> (raw)
In-Reply-To: <201202151225.13673.arekm@maven.pl>
On Wed, Feb 15, 2012 at 12:25:13PM +0100, Arkadiusz Miśkiewicz wrote:
>
> 3.0.17 kernel, 800GB fs, fresh boot, mount of /home at boot (so no daemons
> running yet), and :
>
> [ 17.768459] XFS (md3): Starting recovery (logdev: internal)
> [ 872.427061] XFS (md3): Ending recovery (logdev: internal)
>
> That mount was after (unfortunate) machine reset while it was doing many
> things.
>
> The question is - what could take so long in here?
How big is the log? It's entirely possible that your log is full of
modified inodes and so it's having to read them all in first. A
modified inode only takes a couple of hundred bytes in the log, so
even if you have a 100MB log, you can still have a couple of million
dirty inodes in the log that have to be read and replayed.
This has been known for some time, but the worse case (around
15 minutes - what you've seen here - is most I've seen or heard
reported) is relatively rare so there hasn't been any urgency to
solve this:
http://xfs.org/index.php/Improving_Metadata_Performance_By_Reducing_Journal_Overhead#Reducing_Recovery_Time
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-02-16 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 11:25 mount recovery taking quite long time Arkadiusz Miśkiewicz
2012-02-16 0:20 ` Dave Chinner [this message]
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=20120216002036.GV14132@dastard \
--to=david@fromorbit.com \
--cc=arekm@maven.pl \
--cc=xfs@oss.sgi.com \
/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