From: Gionatan Danti <g.danti@assyoma.it>
To: linux-xfs@vger.kernel.org
Subject: Estimate xfs_repair run time
Date: Sat, 19 Aug 2017 12:05:07 +0200 [thread overview]
Message-ID: <22ed5cf73260ae39bf59779b302d8ad3@assyoma.it> (raw)
Hi list,
using XFS on relatively big filesystems (> 8TB) I was wondering if it is
possible to estimate how much time an emergency "xfs_repair" would take.
Some specific questions:
- will total time depend on how much the filesystem is filled (I think
so...)?
- will total time depend on how data are layed on the physical disks
(ie: fragmented vs sequential)?
- will total time scale down with increasing spindle count (ie: single
disk vs 4-way RAID10)?
On a related question: I generally use LVM to segregate/isolate my
virtual machine images. In this manner, even a completely blowed up
filesystem on one LV can not affect other LV.
How do you feel using a single big LV + XFS + preallocated RAW disk
images? Can a problem on the main XFS filesystem be contained on only
some VM files, or it really risks to destroy the entire filesystem?
Thank you all.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next reply other threads:[~2017-08-19 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 10:05 Gionatan Danti [this message]
2017-08-19 12:14 ` Estimate xfs_repair run time 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
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=22ed5cf73260ae39bf59779b302d8ad3@assyoma.it \
--to=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 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.