From: Dave Chinner <david@fromorbit.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair has been running for a very long time, no disk IO.
Date: Tue, 9 Apr 2013 22:02:36 +1000 [thread overview]
Message-ID: <20130409120236.GL17758@dastard> (raw)
In-Reply-To: <20130409121726.6342519e@harpe.intellique.com>
On Tue, Apr 09, 2013 at 12:17:26PM +0200, Emmanuel Florac wrote:
>
> On a quite badly mangled filesystem, xfs_repair (v. 3.1.4) seems to
> never end. It has run for 16 hours with absolutely no disk activity.
>
> Usually xfs_repair takes much less than one hour on a similar (9 TB)
> filesystem.
>
> I know I should try the latest version. What else can be wrong?
> What should I try?
Either use the latest version, or use the -P option.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-09 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 10:17 xfs_repair has been running for a very long time, no disk IO Emmanuel Florac
2013-04-09 12:02 ` Dave Chinner [this message]
2013-04-09 12:30 ` Emmanuel Florac
2013-04-09 12:54 ` Dave Chinner
2013-04-09 17:51 ` Emmanuel Florac
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=20130409120236.GL17758@dastard \
--to=david@fromorbit.com \
--cc=eflorac@intellique.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