From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Ben Myers <bpm@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Weird message from xfs_repair
Date: Thu, 2 May 2013 08:50:24 +0200 [thread overview]
Message-ID: <20130502085024.2a1d096c@galadriel.home> (raw)
In-Reply-To: <518181E1.2000604@sandeen.net>
Le Wed, 01 May 2013 15:58:09 -0500 vous écriviez:
> Several of those internal cache housekeeping messages can be
> alarming. Indeed anything out of the ordinary during repair
> is alarming to most users. ;)
>
Well I've had xfs_repair happily wiping several terabytes of data in
the past, so I'm easily concerned :) But I supposed this is mostly
related to the fact I was running a pre-release.
> Emmanuael - if another xfs_repair pops out the same error,
> then capturing a metadump of the fs would probably let someone
> look into it. Someone who has time, that is. ;)
In that case the filesystem was in extremely poor shape with lots of
errors I've never seen before, and a lot of users waiting for it to
come back online. Fortunately recent xfs_repair seem to be reliable
enough.
--
------------------------------------------------------------------------
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
prev parent reply other threads:[~2013-05-02 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 18:06 Weird message from xfs_repair Emmanuel Florac
2013-05-01 19:43 ` Ben Myers
2013-05-01 20:58 ` Eric Sandeen
2013-05-02 6:50 ` Emmanuel Florac [this message]
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=20130502085024.2a1d096c@galadriel.home \
--to=eflorac@intellique.com \
--cc=bpm@sgi.com \
--cc=sandeen@sandeen.net \
--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