stud2000 Posted January 31, 2022 Share Posted January 31, 2022 (edited) After reboot I have some troubles with one drive. Changed cable and this happend xfs_repair /dev/md2 -n Spoiler xfs_repair /dev/md2 -n Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_icount 456064, counted 32 sb_ifree 453, counted 29 sb_fdblocks 1569863494, counted 1952984861 - 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 - 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 = 4 - agno = 3 - agno = 6 - agno = 7 - agno = 5 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 /dev/md2 Spoiler xfs_repair /dev/md2 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_icount 456064, counted 32 sb_ifree 453, counted 29 sb_fdblocks 1569863494, counted 1952984861 - 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 - 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 = 4 - agno = 1 - agno = 5 - agno = 6 - agno = 7 - agno = 3 Phase 5 - rebuild AG headers and trees... - 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... SB summary counter sanity check failed Metadata corruption detected at 0x477f6b, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 SB summary counter sanity check failed Metadata corruption detected at 0x477f6b, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair. re-run didn't affect the result Also tried to update unraid version to 6.10.0-rc2 and re-run xfs_repair, I had same result fileserver-diagnostics-20220131-2039.zip Edited January 31, 2022 by stud2000 Quote Link to comment
JorgeB Posted January 31, 2022 Share Posted January 31, 2022 That looks like a xfs_repair issue, though it could be the result of bad hardware, run memtest if no issues are detected you can try to report it to the xfs mailing list. Quote Link to comment
stud2000 Posted February 1, 2022 Author Share Posted February 1, 2022 memtest is good 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.