我遇到了1 TB XFS LVM逻辑卷的问题。 这以前是在发生IO错误的物理卷上，所以我使用“pvmove”来迁移到新的磁盘。 迁移后，我可以读取和写入卷，但开始看到“结构需要清理”的错误。 所以我决定卸载卷并运行xfs_repair。
这从下面的消息开始（我已经用“<snipped>”replace了一些经常重复的冗余消息以减less文本的数量）：
Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 entry "/rca.orca_gui_find.indexcache.2012-11-13T22:29:05-05:00.snapshot.gz" at block 147 clearing inode number in entry at offset 2912... entry at block 147 offset 2912 in directory inode 1893017 has illegal name "/rca.orca_gui <snipped> entry at block 0 offset 1616 in directory inode 3728154 has illegal name "/andler.html.zh cleared inode 3728972 imap claims a free inode 3729023 is in use, correcting imap and clearing inode cleared inode 3729023 <snipped> bad magic number 0x0 on inode 3729024 bad version number 0x0 on inode 3729024 <snipped> entry "/gi.html.en" at block 0 offset 696 in directory inode 3729503 references invalid i clearing inode number in entry at offset 968... <snipped> entry at block 0 offset 968 in directory inode 3729503 has illegal name "/taccess.html": will junk block no . entry for directory 3996998 no .. entry for directory 3996998 problem with directory contents in inode 3996998 cleared inode 3996998 bad directory block magic # 0 in block 0 for directory inode 3997000 <snipped> agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 bad directory block magic # 0 in block 0 for directory inode 4003024 corrupt block 0 in directory inode 4003024 will junk block no . entry for directory 4003024 no .. entry for directory 4003024 entry "Authoring.pod" at block 0 offset 160 in directory inode 14276983 references free i clearing inode number in entry at offset 160... entry "Base.pm" at block 0 offset 216 in directory inode 14276983 references free inode 3 <snipped> - agno = 1 entry "wireless" at block 0 offset 688 in directory inode 2207138636 references free inod clearing inode number in entry at offset 688... entry "xfrm" at block 0 offset 728 in directory inode 2207138636 references free inode 39 clearing inode number in entry at offset 728... entry "seq" at block 0 offset 64 in directory inode 2207276722 references free inode 4001 clearing inode number in entry at offset 64... - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... 自从昨天以来，xfs_repair已经停止输出新的东西到屏幕上。 我用strace检查，但我没有看到任何活动。 xfs_repair进程仍然存在于进程表中，消耗内存，但没有CPU。
那么它在做什么？ 我应该让它运行，还是终止这个过程？ 我能够使用现有的文件系统，还是需要重新使用新的干净的XFS卷？
我想我可以做的就是停止这个过程，重启机器，看看“修复”的部分是否可以安装….如果没有问题。 如果不是，那么您可以重新启动该过程。
你试图转换的分区有多大？