[SOLVED]Xfs disk error

[goinsnoopin]

I could use some assistance....logs filling up seems to be an issue with disk md2.  Stopped array and entered maintenance mode....did xfs check on all disks...this confirms errors with disk 2.   Here is output for xfs_repair -n...looking for advice on next step before proceeding.

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
Metadata corruption detected at xfs_agf block 0x1/0x200
flfirst 118 in agf 0 too large (max = 118)
agf 118 freelist blocks bad, skipping freelist scan
sb_fdblocks 131031877, counted 131031871
        - 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 = 3
        - agno = 2
        - agno = 0
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.

tower-diagnostics-20170801-2022.zip

Edited August 2, 2017 by goinsnoopin

[goinsnoopin]

Ran xfs_repair with verbose switch....here is more detailed output:

 

 

Phase 1 - find and verify superblock... - block cache size set to 3029920 entries Phase 2 - using internal log - zero log... zero_log: head block 312683 tail block 312683 - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0x1/0x200 flfirst 118 in agf 0 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan sb_fdblocks 131031877, counted 131031871 - 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 ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - 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 Tue Aug 1 22:33:39 2017 Phase Start End Duration Phase 1: 08/01 22:33:18 08/01 22:33:23 5 seconds Phase 2: 08/01 22:33:23 08/01 22:33:23 Phase 3: 08/01 22:33:23 08/01 22:33:32 9 seconds Phase 4: 08/01 22:33:32 08/01 22:33:32 Phase 5: Skipped Phase 6: 08/01 22:33:32 08/01 22:33:39 7 seconds Phase 7: 08/01 22:33:39 08/01 22:33:39 Total run time: 21 seconds

[JorgeB]

Assuming the disk is OK since all SMART reports are 0 size files on your diags, remove the -n (no modify) flag and run xfs_repair again.

[goinsnoopin]

Thanks Johnnie...ran the xfs_repair....everything seems good!

 

Thanks!