xfs_repair は xfs_repair -n に従ってファイルシステムを回復しません。

xfs_repair は xfs_repair -n に従ってファイルシステムを回復しません。

クラッシュ後に破損したファイルシステムがありますxfs_repair -n。ページに記載されているようにxfs_repair man損傷xfs_repair -nが検出された場合は存在し、状態1を返します。そのため、xfs_repairファイルシステムで実行してからやり直しxfs_repair -nてください。終了ステータスはまだ1です。

~によるとLinux管理用のXFS第4章xfs_repairすべての問題を解決するには、最大3回の実行が必要になることがあります。これまでこれを4回実行しましたが、終了ステータスはxfs_repair -nまだ1です。ファイルシステムがマウントされているので、原則としてデータにアクセスできますが、実際に何が破損しているのか、どのように解決できるのかを知るための別のオプションがあるかどうか疑問に思います。

出力xfs_repair -n

Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
Memory available for repair (2048MB) may not be sufficient.
At least 2368MB is needed to repair this filesystem efficiently
If repair fails due to lack of memory, please
turn prefetching off (-P) to reduce the memory footprint.
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - 22:27:46: scanning filesystem freespace - 32 of 32 allocation groups done
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - 22:27:46: scanning agi unlinked lists - 32 of 32 allocation groups done
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 30
        - agno = 15
        - agno = 16
        - agno = 31
        - agno = 1
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 2
        - agno = 20
        - agno = 21
        - agno = 3
        - agno = 22
        - agno = 4
        - agno = 23
        - agno = 24
        - agno = 5
        - agno = 25
        - agno = 6
        - agno = 26
        - agno = 27
        - agno = 7
        - agno = 28
        - agno = 8
        - agno = 29
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - 22:27:54: process known inodes and inode discovery - 4166208 of 4166208 inodes done
        - process newly discovered inodes...
        - 22:27:54: process newly discovered inodes - 32 of 32 allocation groups done
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - 22:27:55: setting up duplicate extent list - 32 of 32 allocation groups done
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 15
        - agno = 30
        - agno = 16
        - agno = 1
        - agno = 17
        - agno = 31
        - agno = 18
        - agno = 2
        - agno = 19
        - agno = 3
        - agno = 20
        - agno = 21
        - agno = 4
        - agno = 22
        - agno = 5
        - agno = 23
        - agno = 6
        - agno = 24
        - agno = 7
        - agno = 25
        - agno = 8
        - agno = 26
        - agno = 9
        - agno = 10
        - agno = 27
        - agno = 11
        - agno = 28
        - agno = 12
        - agno = 29
        - agno = 13
        - agno = 14
        - 22:28:03: check for inodes claiming duplicate blocks - 4166208 of 4166208 inodes done
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

これは最後の実行の出力ですxfs_repair

Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
Memory available for repair (2048MB) may not be sufficient.
At least 2368MB is needed to repair this filesystem efficiently
If repair fails due to lack of memory, please
turn prefetching off (-P) to reduce the memory footprint.
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - 22:31:08: scanning filesystem freespace - 32 of 32 allocation groups done
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - 22:31:08: scanning agi unlinked lists - 32 of 32 allocation groups done
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 30
        - agno = 15
        - agno = 16
        - agno = 31
        - agno = 1
        - agno = 17
        - agno = 18
        - agno = 2
        - agno = 19
        - agno = 20
        - agno = 3
        - agno = 21
        - agno = 4
        - agno = 22
        - agno = 5
        - agno = 23
        - agno = 6
        - agno = 24
        - agno = 7
        - agno = 25
        - agno = 8
        - agno = 26
        - agno = 9
        - agno = 27
        - agno = 10
        - agno = 28
        - agno = 29
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - 22:31:16: process known inodes and inode discovery - 4166208 of 4166208 inodes done
        - process newly discovered inodes...
        - 22:31:16: process newly discovered inodes - 32 of 32 allocation groups done
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - 22:31:17: setting up duplicate extent list - 32 of 32 allocation groups done
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 15
        - agno = 30
        - agno = 16
        - agno = 31
        - agno = 1
        - agno = 17
        - agno = 18
        - agno = 2
        - agno = 19
        - agno = 3
        - agno = 20
        - agno = 4
        - agno = 21
        - agno = 5
        - agno = 6
        - agno = 22
        - agno = 7
        - agno = 8
        - agno = 23
        - agno = 24
        - agno = 9
        - agno = 25
        - agno = 10
        - agno = 11
        - agno = 26
        - agno = 12
        - agno = 27
        - agno = 13
        - agno = 28
        - agno = 14
        - agno = 29
        - 22:31:25: check for inodes claiming duplicate blocks - 4166208 of 4166208 inodes done
Phase 5 - rebuild AG headers and trees...
        - 22:31:28: rebuild AG headers and trees - 32 of 32 allocation groups done
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done

ベストアンサー1

問題は次のとおりです。Ext4 fsを使用する別のものがあります、xfstools用の32ビットバイナリを含むリカバリCDが原因で発生しました(カーネル自体が64ビットにもかかわらず)。

そのため、最終的にルートパーティションをマウントし(問題なし)、そこでxfs_repair -n実行するためにルートパーティションに移動しました。予想通り、0 が返されました。

おすすめ記事