All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael L. Semon" <mlsemon35@gmail.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>, xfs <xfs@oss.sgi.com>
Subject: Re: very long log recovery at mount
Date: Wed, 21 Oct 2015 14:39:25 -0400	[thread overview]
Message-ID: <5627DBDD.3060702@gmail.com> (raw)
In-Reply-To: <201510211127.52794.arekm@maven.pl>

On 10/21/15 05:27, Arkadiusz Miśkiewicz wrote:
>
> Hi.
>
> I got such situation, fresh boot, 4.1.10 kernel, init scripts start mounting
> filesystems. One fs wasn't very lucky:
>
> [   15.979538] XFS (md3): Mounting V4 Filesystem
> [   16.256316] XFS (md3): Ending clean mount
> [   28.343346] XFS (md4): Mounting V4 Filesystem
> [   28.629918] XFS (md4): Ending clean mount
> [   28.662125] XFS (md5): Mounting V4 Filesystem
> [   28.980142] XFS (md5): Ending clean mount
> [   29.049421] XFS (md6): Mounting V4 Filesystem
> [   29.447725] XFS (md6): Starting recovery (logdev: internal)
> [ 4517.327332] XFS (md6): Ending recovery (logdev: internal)
>
> It took over 1h to mount md6 filesystem.
>
> Questions:
> - is it possible to log how much data is needed to be recovered from log? Some
> data that would give a hint on how big this is (and thus rough estimate on how
> long it will take). Not sure if that's known at time when this message is
> being printed.
>
> XFS (md6): Starting recovery (logdev: internal, to recover: xyzMB (?))
>
> - now such long mount time is almost insane, so I wonder why could be the
> reason. Is the process multithreaded, single threaded? cpus were idle
>

My old PC used to suffer from intermittently long mount times, and I wrote a
one-character patch to fix that issue:

http://oss.sgi.com/archives/xfs/2015-01/msg00183.html

I'm putting it out there only to ask the list if wrapped-log handling could be
the issue here.  Don't try the patch without good reason:  I've tested it only
as late as kernel 3.18.22, on 32-bit Linux with MBR and GPT partitions, not
much of a test matrix.

Thanks!

Michael

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-10-21 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  9:27 very long log recovery at mount Arkadiusz Miśkiewicz
2015-10-21 18:39 ` Michael L. Semon [this message]
2015-10-23  7:05 ` Dave Chinner
2015-10-23  7:22   ` Arkadiusz Miśkiewicz
2015-10-23 21:30     ` Dave Chinner

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=5627DBDD.3060702@gmail.com \
    --to=mlsemon35@gmail.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 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.