From: Eric Sandeen <sandeen@sandeen.net>
To: Dragon <Sunghost@gmx.de>, xfs@oss.sgi.com
Subject: Re: XFS Repair hangs at inode repair in phase3
Date: Tue, 24 Jun 2014 10:35:44 -0500 [thread overview]
Message-ID: <53A99AD0.4000003@sandeen.net> (raw)
In-Reply-To: <trinity-64075195-5d6c-40f8-97ba-cc348261c69f-1403619853159@3capp-gmx-bs44>
You can always try:
# git clone git://oss.sgi.com/xfs/cmds/xfsprogs.git
# cd xfsprogs
# git checkout v3.2.0
# make
# repair/xfs_repair -n /dev/md2
-Eric
On 6/24/14, 9:24 AM, Dragon wrote:
> Hello Eric,
> ok will never use xfs_check ;). Yes i saw option -P but i though if i
> desabled that test, i will never get fix those problems. The Version
> is from Debian Wheezy stable, so why it is such old, when it is that
> important :do not understand this from debianmaintainer...: So what
> could i do to use latest Version under Debian Wheezy? Normaly i use
> the package system.. Any risk to loos all my data? Where came the
> Problem from? If the version is such old, was the md2 created out of
> that, or are there only the tools in it?
> Thx
>
> On 6/24/14, 8:01 AM, Dragon wrote:
>
> Hello, i have a fresh install Debian Wheezy with software raid as md2 for my files. MD2 is nealry full of 8TB and i wanted to migrate the data to a newier system. While copy files i got an message that i have to run xfs_repair. I first run xfs_check but it eats up all my 11GB memory and the system stalls.
>
> Yep, xfs_check doesn't scale and is on the way to deprecation.
>
> Then i run xfs_repair -n /dev/md2 but it hangs each time add: problem with directory contens in inode 2147997719 - would have cleared inode 2147997719. If i break this and restart, it hangs at the same position. System seems to do nothing over hours.
>
> You might try the -P option to repair. -P Disable prefetching of inode and directory blocks. Use this option if you find xfs_repair gets stuck and stops proceeding. If that works, it likely indicates a bug, but it might get you going.
>
> Some Infos: xfsprogs in Version 3.1.7+b1
>
> And that's a 3-year old xfsprogs, so an upgrade might help, too. -Eric
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-24 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 14:24 XFS Repair hangs at inode repair in phase3 Dragon
2014-06-24 15:35 ` Eric Sandeen [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 22:15 Dragon
2014-06-24 23:08 ` Stan Hoeppner
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 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=53A99AD0.4000003@sandeen.net \
--to=sandeen@sandeen.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.