From: Tomek Kruszona <bloodyscarion@gmail.com>
To: xfs@oss.sgi.com
Subject: xfs_repair stops on "traversing filesystem..."
Date: Thu, 09 Jul 2009 16:13:11 +0200 [thread overview]
Message-ID: <4A55FAF7.5040908@gmail.com> (raw)
Hello!
I have a little problem with XFS filesystem that I have on one of my
machines. I try to make xfs_repair that was not making any problems
before, but xfs_repair stops on:
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
CPU usage grows up to 100%. I left it in the night hoping it will finish
job till morning, but the situation hasn't changed...
System is Debian Lenny with current updates and custom 2.6.30.1 kernel
xfsprogs-2.9.8. Filesysystem is placed on LVM2 Logical Volume.
I upgraded xfsprogs to 3.0.2 version and the problem still persists.
Then I reverted to 2.9.8 package from Debian Lenny.
Switching back to debian default 2.6.26 kernel doesn't help too.
I can mount this filesystem and operate on it.
Data on this system is not so crucial, because it's backup/testing
machine, but it would be great to keep this data, because synchronizing
14TB of data will take some time.
Output from xfs_info:
# xfs_info /mnt/storage/
meta-data=/dev/mapper/p02bvg-p02blv isize=256 agcount=32,
agsize=268435455 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=8410889216, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
Any ideas how to make xfs_repair working again?
Best regards,
Tomasz Kruszona
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-07-09 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 14:13 Tomek Kruszona [this message]
2009-07-09 14:54 ` xfs_repair stops on "traversing filesystem..." Eric Sandeen
2009-07-09 15:03 ` Tomek Kruszona
2009-07-10 5:28 ` Eric Sandeen
2009-07-10 7:27 ` Tomek Kruszona
2009-07-10 14:35 ` Eric Sandeen
2009-07-10 20:17 ` Eric Sandeen
2009-07-10 21:02 ` Tomek Kruszona
2009-07-10 21:15 ` Eric Sandeen
2009-07-10 23:44 ` Tomek Kruszona
2009-07-11 0:36 ` 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=4A55FAF7.5040908@gmail.com \
--to=bloodyscarion@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