All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-xfs@vger.kernel.org, g.danti@assyoma.it
Subject: Re: Estimate xfs_repair run time
Date: Sun, 20 Aug 2017 07:05:50 +0200	[thread overview]
Message-ID: <128ec64d954acd2b8760d017fd16db46@assyoma.it> (raw)
In-Reply-To: <20170820020438.GQ10621@dastard>

Hi Dave,

Il 20-08-2017 04:04 Dave Chinner ha scritto:
> 
> 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...

ok, so I at least need to try & see how well xfs_repair does on a clean 
filesystem.

Thanks.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2017-08-20  5:05 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
2017-08-20  5:05             ` Gionatan Danti [this message]
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=128ec64d954acd2b8760d017fd16db46@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --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 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.