From: Emmanuel Florac <eflorac@intellique.com>
To: Gregory Farnum <gregory.farnum@dreamhost.com>
Cc: xfs@oss.sgi.com
Subject: Re: EFSCORRUPTED on mount?
Date: Mon, 21 Nov 2011 22:52:39 +0100 [thread overview]
Message-ID: <20111121225239.12769adb@galadriel.home> (raw)
In-Reply-To: <CAF3hT9B8-ou-4RhfCkfFWTwwB_tb7nWSP-5pgP3G6oTE+1gAvA@mail.gmail.com>
Le Mon, 21 Nov 2011 10:06:20 -0800 vous écriviez:
> Is there something useful I can do about this? Data I can provide to
> help track down what broke?
xfs_check is mostly useless nowadays, use "xfs_repair -n" instead. At
this stage, there's probably not much you can do but an "xfs_repair -L"
to zero the log. Hope for the better.
In my opinion some service using the filesystem (ceph?) got stuck at
reboot and prevented proper unmounting of the fs. Or maybe was tehre
some IO error; you could check your logs for this too.
--
------------------------------------------------------------------------
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:[~2011-11-21 21:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 18:06 EFSCORRUPTED on mount? Gregory Farnum
2011-11-21 21:52 ` Emmanuel Florac [this message]
2011-11-21 22:13 ` Ben Myers
2011-11-22 0:21 ` Gregory Farnum
2011-11-22 1:41 ` Dave Chinner
2011-11-22 18:47 ` Gregory Farnum
2011-11-22 18:52 ` Eric Sandeen
2011-11-22 19:29 ` Gregory Farnum
2011-11-22 21:53 ` Eric Sandeen
2011-11-22 22:55 ` Christoph Hellwig
2011-11-23 0:03 ` Gregory Farnum
2011-11-23 15:51 ` Christoph Hellwig
2011-11-22 22:11 ` Christoph Hellwig
2011-11-22 8:06 ` Emmanuel Florac
2011-11-22 15:06 ` Eric Sandeen
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=20111121225239.12769adb@galadriel.home \
--to=eflorac@intellique.com \
--cc=gregory.farnum@dreamhost.com \
--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