public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Sean Caron <scaron@umich.edu>
Cc: xfs@oss.sgi.com
Subject: Re: What to do when... xfs_repair hangs?
Date: Sun, 1 Jun 2014 22:40:24 +0200	[thread overview]
Message-ID: <20140601224024.628372c5@galadriel.home> (raw)
In-Reply-To: <CAA43vkUBF3q-F6XYTPTVx43KXg_3_COgaK8wtHxRynshOT9smg@mail.gmail.com>

Le Sun, 1 Jun 2014 12:21:55 -0400 vous écriviez:

> Since Dave is saying it's OK to try re-running xfs_repair; it'll just
> pick up where it left off; let me give it another pass and see if it
> manages to complete, or if it segfaults out again. I guess it it
> poops out a second time, maybe we'll just want to consider rebuilding
> the filesystem and restoring from our copies?

You should definitely try a more up-to-date version of xfs_repair
first. In case you're not afraid of running a binary from an unkown
source, please find a 3.1.11 binary here:

http://update.intellique.com/pub/xfsrepair.tar.gz

-- 
------------------------------------------------------------------------
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

  reply	other threads:[~2014-06-01 20:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 19:49 What to do when... xfs_repair hangs? Sean Caron
2014-05-30 21:30 ` Brian Foster
2014-05-31  0:01 ` Dave Chinner
2014-06-01 16:21   ` Sean Caron
2014-06-01 20:40     ` Emmanuel Florac [this message]
2014-06-01 22:48     ` Dave Chinner
2014-06-02 18:32       ` Sean Caron

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=20140601224024.628372c5@galadriel.home \
    --to=eflorac@intellique.com \
    --cc=scaron@umich.edu \
    --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