From: Dave Chinner <david@fromorbit.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>, linux-xfs@vger.kernel.org
Subject: Re: Estimate xfs_repair run time
Date: Sun, 20 Aug 2017 12:04:38 +1000 [thread overview]
Message-ID: <20170820020438.GQ10621@dastard> (raw)
In-Reply-To: <a42886b91433dcf4d7fdd3f541f2374a@assyoma.it>
On Sat, Aug 19, 2017 at 06:39:58PM +0200, Gionatan Danti wrote:
> >{yes, yes, depends on which spindle(s) metadata end up on and how many
> >files cross AGs} in that order. :)
>
> Mmm ok, as expected :)
> Do you have any direct experience of xfs_repair run times on big and
> full XFS filesystems?
Yes. And there's no hard and fast number we can give you because
runtime will depends on the amount and density of the metadata, the
speed of the underlying storage, how much RAM you have and how badly
corrupted the filesystem is.
IOWs, runtime can vary from a few minutes to a few days as you vary
those parameters, and there's really no way to tell in advance where
in that massive variance any specific production filesystem will
land.
Doing a test run (xfs_repair -n) to get a ballpark figure during a
planned downtime period is the only way you'll get any idea of the
*best case* repair duration on a *clean* filesystem. But the moment
repair finds corruptions, all guesses you can make about runtime go
out the window...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-08-20 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 10:05 Estimate xfs_repair run time Gionatan Danti
2017-08-19 12:14 ` Gionatan Danti
2017-08-19 15:48 ` Darrick J. Wong
2017-08-19 16:15 ` Gionatan Danti
2017-08-19 16:20 ` Darrick J. Wong
2017-08-19 16:39 ` Gionatan Danti
2017-08-20 2:04 ` Dave Chinner [this message]
2017-08-20 5:05 ` Gionatan Danti
2017-08-20 2:10 ` Eric Sandeen
2017-08-20 5:07 ` Gionatan Danti
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=20170820020438.GQ10621@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=g.danti@assyoma.it \
--cc=linux-xfs@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