March 7, 20206 yr Hello, I keep getting this error so have included my diagnostics as suggetsed by the Fix Common Problems app. Any help warmly welcomed Thank you. Adam server-diagnostics-20200307-1103.zip
March 7, 20206 yr Author Ok, done: Phase 1 - find and verify superblock... - block cache size set to 1493528 entries Phase 2 - using internal log - zero log... zero_log: head block 4025 tail block 4025 - 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 bogus .. inode number (0) in directory inode 7516192864, would clear inode number - 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 = 2 - agno = 3 - agno = 6 - agno = 7 - agno = 10 - agno = 11 bogus .. inode number (0) in directory inode 7516192864, would clear inode number - agno = 9 - agno = 8 - agno = 4 - agno = 5 - agno = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry "ANY!" in dir ino 4294967392 doesn't have a .. entry, will set it in ino 7516192864. - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 would set .. in sf dir inode 7516192864 to 4294967392 - 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 Sat Mar 7 12:58:46 2020 Phase Start End Duration Phase 1: 03/07 12:58:43 03/07 12:58:43 Phase 2: 03/07 12:58:43 03/07 12:58:44 1 second Phase 3: 03/07 12:58:44 03/07 12:58:46 2 seconds Phase 4: 03/07 12:58:46 03/07 12:58:46 Phase 5: Skipped Phase 6: 03/07 12:58:46 03/07 12:58:46 Phase 7: 03/07 12:58:46 03/07 12:58:46 Total run time: 3 seconds
March 7, 20206 yr Author Thanks, look ok now? Phase 1 - find and verify superblock... - block cache size set to 1493528 entries Phase 2 - using internal log - zero log... zero_log: head block 4025 tail block 4025 - 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 bogus .. inode number (0) in directory inode 7516192864, clearing inode number - 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 = 5 - agno = 9 - agno = 10 - agno = 3 - agno = 7 - agno = 8 bogus .. inode number (0) in directory inode 7516192864, clearing inode number - agno = 2 - agno = 4 - agno = 11 - agno = 6 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry "ANY!" in dir ino 4294967392 doesn't have a .. entry, will set it in ino 7516192864. - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 setting .. in sf dir inode 7516192864 to 4294967392 Metadata corruption detected at 0x462e2c, inode 0x1c0000060 data fork xfs_repair: warning - iflush_int failed (-117) - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Sat Mar 7 13:20:56 2020 Phase Start End Duration Phase 1: 03/07 13:20:10 03/07 13:20:19 9 seconds Phase 2: 03/07 13:20:19 03/07 13:20:20 1 second Phase 3: 03/07 13:20:20 03/07 13:20:22 2 seconds Phase 4: 03/07 13:20:22 03/07 13:20:22 Phase 5: 03/07 13:20:22 03/07 13:20:22 Phase 6: 03/07 13:20:22 03/07 13:20:22 Phase 7: 03/07 13:20:22 03/07 13:20:22 Total run time: 12 seconds done
March 27, 20206 yr Author Hi, I have followed this procedure a couple of times now but am still getting the same issue. Any ideas? Thank you. Adam server-diagnostics-20200327-1030.zip
Archived
This topic is now archived and is closed to further replies.