rvoosterhout Posted November 22, 2021 Author Share Posted November 22, 2021 The check filesystem: Phase 1 - find and verify superblock... - block cache size set to 1011800 entries Phase 2 - using internal log - zero log... zero_log: head block 171120 tail block 171120 - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - 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 = 6 - agno = 9 - agno = 3 - agno = 4 - agno = 5 - agno = 7 - agno = 2 - agno = 10 - agno = 11 - agno = 8 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon Nov 22 21:27:45 2021 Phase Start End Duration Phase 1: 11/22 21:27:44 11/22 21:27:44 Phase 2: 11/22 21:27:44 11/22 21:27:44 Phase 3: 11/22 21:27:44 11/22 21:27:45 1 second Phase 4: 11/22 21:27:45 11/22 21:27:45 Phase 5: Skipped Phase 6: 11/22 21:27:45 11/22 21:27:45 Phase 7: 11/22 21:27:45 11/22 21:27:45 Total run time: 1 second Quote Link to comment
ChatNoir Posted November 22, 2021 Share Posted November 22, 2021 Run it again without -n (no modify). As is, it was just a test run. Once it is done, check for a lost+found share. Quote Link to comment
rvoosterhout Posted November 22, 2021 Author Share Posted November 22, 2021 15 minutes ago, ChatNoir said: Run it again without -n (no modify). As is, it was just a test run. Once it is done, check for a lost+found share. I ran it witout the -n, but with -v. No lost+found share has been created nor is there a lost+found share on the drive. Quote Link to comment
ChatNoir Posted November 22, 2021 Share Posted November 22, 2021 13 minutes ago, rvoosterhout said: No lost+found share has been created nor is there a lost+found share on the drive. It means that no files were misplaced during the fix. 👍 Quote Link to comment
rvoosterhout Posted November 22, 2021 Author Share Posted November 22, 2021 6 minutes ago, ChatNoir said: It means that no files were misplaced during the fix. 👍 Awesome! I'm already running my dockers and vm's. It seems everything is running fine so far. 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.