public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Dragon <Sunghost@gmx.de>, xfs@oss.sgi.com
Subject: Re: XFS Repair hangs at inode repair in phase3
Date: Tue, 24 Jun 2014 18:08:37 -0500	[thread overview]
Message-ID: <53AA04F5.5080000@hardwarefreak.com> (raw)
In-Reply-To: <trinity-ffefb824-acab-4879-8870-2861ffb3bad2-1403648145455@3capp-gmx-bs71>

On 6/24/2014 5:15 PM, Dragon wrote:
> Hi,
> yes read this, but i am new and dont know what this command will do and i dont 
> want to lost my data. I read in the net, that some people couldnt start or boot 
> from that disk, after running xfs_repair. I looked for a upgrade to latest 
> xfsprogs version, but it seems difficult for amd64 systems. Do you have a 
> changelog to latest version, could my installed version be ok, or better not to use?
> Thx Stan and Eric

# xfs_repair -n -P /dev/device

Post the output in your next reply, assuming it doesn't hang again.

Cheers,

Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-06-24 23:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 22:15 XFS Repair hangs at inode repair in phase3 Dragon
2014-06-24 23:08 ` Stan Hoeppner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-27  7:42 Dragon
2014-06-26 19:17 Dragon
2014-06-26 23:32 ` Stan Hoeppner
2014-06-27  0:02 ` Dave Chinner
2014-06-24 23:41 Dragon
2014-06-24 20:02 Dragon
2014-06-24 21:29 ` Stan Hoeppner
2014-06-24 19:07 Dragon
2014-06-24 15:43 Dragon
2014-06-24 18:54 ` Stan Hoeppner
2014-06-24 14:24 Dragon
2014-06-24 15:35 ` Eric Sandeen
2014-06-24 13:01 Dragon
2014-06-24 14:15 ` 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=53AA04F5.5080000@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=Sunghost@gmx.de \
    --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