From: Emmanuel Florac <eflorac@intellique.com>
To: Roel van Meer <rolek@bokxing.nl>
Cc: xfs@oss.sgi.com
Subject: Re: advice for repair after IO error on raid device
Date: Tue, 22 Jun 2010 18:31:54 +0200 [thread overview]
Message-ID: <20100622183154.24e84e0d@harpe.intellique.com> (raw)
In-Reply-To: <cone.1277218412.674723.87295.1001@bork.lsof.org>
Le Tue, 22 Jun 2010 16:53:32 +0200
Roel van Meer <rolek@bokxing.nl> écrivait:
> If someone could confirm (or reject) that, that would be great.
Confirmation granted.
> (By the way, is it necessary to run xfs_repair with -n first? If not,
> are there advantages that would justify the extra time it takes?)
It will indicate what modifications he would have done, before actually
doing them... Like "inode 038953095 corrupted, would remove it" then
"directory not connected, would move content moved to lost+found"
I found that usually xfs_repair is quit quick and never takes much more
than a couple of minutes (even on very big arrays) so you have no valid
reason to skip the "xfs_repair -n" part.
It may be nice to dump the filesystem metadata with xfs_metadump
prior to using xfs_repair too. In the case where the repair's really
gone bad, you could at least revert to the prior less broken state using
xfs_mdrestore...
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-22 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 14:36 advice for repair after IO error on raid device Roel van Meer
2010-06-22 14:53 ` Roel van Meer
2010-06-22 15:29 ` Michael Weissenbacher
2010-06-22 16:31 ` Emmanuel Florac [this message]
2010-06-22 16:07 ` Michael Monnerie
2010-06-22 16:35 ` Emmanuel Florac
2010-06-24 8:28 ` advice for repair after IO error on raid device [SOLVED] Roel van Meer
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=20100622183154.24e84e0d@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=rolek@bokxing.nl \
--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