From: Christoph Hellwig <hch@infradead.org>
To: Pavol Zibrita <pavol.zibrita@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair gets stuck on phase3
Date: Mon, 12 Dec 2011 08:12:55 -0500 [thread overview]
Message-ID: <20111212131255.GA15481@infradead.org> (raw)
In-Reply-To: <CAENWQX0FgOrTiDVaictZkNfnpBR40DWrHsWrysPHDvdoqvcw5A@mail.gmail.com>
On Sun, Dec 11, 2011 at 09:20:14PM +0000, Pavol Zibrita wrote:
> I tried various option for xfs_repair, but when in phase 3, it just
> calculates and calculates and does nothing.
> CPU is used around 97%.
>
> Examining the system with knoppix live cd.
>
> Attaching logs with the outputs.
> log.log: xfs_repair
> p-log.log: with -P
> strace-log.log stracing xfs_repair
>
> After using the -L option I can mount the fs, but there are still bugs on
> the filesystem I would like to fix.
>
> Currently, I don't have any other 4TB of space I could move the data to
> make some more drastic changes
> like reformat or so.
As Dave mentioned my fix for loops in the unlinked inode list is a
likely candidate. If you can prepare a dump of the metadata using the
xfs_metadump tool for me I can take a look. If it indeed were the
unlinked inode lists we could also fix your issues fairly easily using
xfs_db.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-12-12 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 21:20 xfs_repair gets stuck on phase3 Pavol Zibrita
2011-12-11 22:27 ` Emmanuel Florac
2011-12-11 22:34 ` Pavol Zibrita
2011-12-12 0:45 ` Dave Chinner
2011-12-12 13:12 ` Christoph Hellwig [this message]
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=20111212131255.GA15481@infradead.org \
--to=hch@infradead.org \
--cc=pavol.zibrita@gmail.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