tillo Posted March 16, 2018 Author Share Posted March 16, 2018 Quote 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 (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - 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 - agno = 1 - agno = 2 - agno = 3 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. When I did it from within unraids webGUI according to the instructions provided by @trurl, I get this output for disk 1. Quote Link to comment
JorgeB Posted March 16, 2018 Share Posted March 16, 2018 Normally still would need to check the exit code or run without -n, but since it was okay before no need. Quote Link to comment
tillo Posted March 16, 2018 Author Share Posted March 16, 2018 Quote root@Nano:~# xfs_repair -n /dev/md1 && echo ${PIPESTATUS[0]} 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 (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - 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 = 1 - agno = 0 - agno = 2 - agno = 3 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. 0 Okey, I did it one more time "xfs_repair -n /dev/md1 && echo ${PIPESTATUS[0]}". this returned the exit code 0 (Se printout above) Is it anything else I should look into. Or should I re-run the parity check, and accept all the error (for this time).And then continue as normal, if no more errors occur after that? Quote Link to comment
JorgeB Posted March 16, 2018 Share Posted March 16, 2018 Probably the option for now. Quote Link to comment
tillo Posted March 16, 2018 Author Share Posted March 16, 2018 Okey, I will do that, thanx for now. Many thanx to you Johnnie and trurl for all the help. Lets hope that everything works now :-D If not you will soon know Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.