mattekure Posted May 21, 2022 Share Posted May 21, 2022 Something crashed and now a bunch of my shares are missing. The logs are filled with this. May 21 17:20:01 Tower kernel: blk_update_request: I/O error, dev loop2, sector 1230432 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 May 21 17:20:01 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 55, rd 5410, flush 0, corrupt 0, gen 0 May 21 17:20:01 Tower kernel: blk_update_request: I/O error, dev loop2, sector 3327584 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 May 21 17:20:01 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 55, rd 5411, flush 0, corrupt 0, gen 0 Any clue what happend? tower-diagnostics-20220521-1720.zip Quote Link to comment
trurl Posted May 21, 2022 Share Posted May 21, 2022 Those logs are about your corrupt docker.img, which is a symptom of your corrupt cache, and the missing shares are those which use cache. Since cache is XFS check filesystem on cache. Be sure to capture the output so you can post it. https://wiki.unraid.net/Manual/Storage_Management#Running_the_Test_using_the_webGui Quote Link to comment
mattekure Posted May 22, 2022 Author Share Posted May 22, 2022 14 hours ago, trurl said: Those logs are about your corrupt docker.img, which is a symptom of your corrupt cache, and the missing shares are those which use cache. Since cache is XFS check filesystem on cache. Be sure to capture the output so you can post it. https://wiki.unraid.net/Manual/Storage_Management#Running_the_Test_using_the_webGui ok. had to wait for the parity check to finish. running the xfs_repair -nv I get the following. Phase 1 - find and verify superblock... - block cache size set to 3079832 entries Phase 2 - using internal log - zero log... zero_log: head block 32959 tail block 32959 - 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 = 3 - agno = 2 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 Sun May 22 08:25:41 2022 Phase Start End Duration Phase 1: 05/22 08:25:37 05/22 08:25:37 Phase 2: 05/22 08:25:37 05/22 08:25:37 Phase 3: 05/22 08:25:37 05/22 08:25:39 2 seconds Phase 4: 05/22 08:25:39 05/22 08:25:39 Phase 5: Skipped Phase 6: 05/22 08:25:39 05/22 08:25:41 2 seconds Phase 7: 05/22 08:25:41 05/22 08:25:41 Total run time: 4 seconds Quote Link to comment
JorgeB Posted May 22, 2022 Share Posted May 22, 2022 Run it again without -n or nothing will done. Quote Link to comment
mattekure Posted May 22, 2022 Author Share Posted May 22, 2022 Phase 1 - find and verify superblock... - block cache size set to 3079832 entries Phase 2 - using internal log - zero log... zero_log: head block 167005 tail block 167005 - 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 - 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 = 1 clearing reflink flag on inode 874966336 clearing reflink flag on inode 874966387 clearing reflink flag on inode 874967432 clearing reflink flag on inode 874967441 clearing reflink flag on inode 875203506 clearing reflink flag on inode 537434009 clearing reflink flag on inode 456271 clearing reflink flag on inode 268699468 clearing reflink flag on inode 268699472 clearing reflink flag on inode 537434010 clearing reflink flag on inode 268699473 clearing reflink flag on inode 456272 clearing reflink flag on inode 268699476 clearing reflink flag on inode 456273 clearing reflink flag on inode 268699485 clearing reflink flag on inode 456275 clearing reflink flag on inode 456276 clearing reflink flag on inode 537607433 clearing reflink flag on inode 456277 clearing reflink flag on inode 268699490 clearing reflink flag on inode 268699491 clearing reflink flag on inode 268699492 clearing reflink flag on inode 268699493 clearing reflink flag on inode 268699494 clearing reflink flag on inode 456278 clearing reflink flag on inode 456280 clearing reflink flag on inode 456281 clearing reflink flag on inode 537607440 clearing reflink flag on inode 537607441 clearing reflink flag on inode 537607446 clearing reflink flag on inode 537607450 clearing reflink flag on inode 537607452 clearing reflink flag on inode 537607453 clearing reflink flag on inode 537607454 clearing reflink flag on inode 537607455 clearing reflink flag on inode 537607458 clearing reflink flag on inode 537607460 clearing reflink flag on inode 537607463 clearing reflink flag on inode 537607465 clearing reflink flag on inode 537607466 clearing reflink flag on inode 537611395 clearing reflink flag on inode 537611404 clearing reflink flag on inode 537611405 clearing reflink flag on inode 537611411 clearing reflink flag on inode 537611454 clearing reflink flag on inode 537612072 clearing reflink flag on inode 537612073 clearing reflink flag on inode 537612089 clearing reflink flag on inode 537612671 clearing reflink flag on inode 537612993 clearing reflink flag on inode 537612994 clearing reflink flag on inode 537612995 clearing reflink flag on inode 537613001 clearing reflink flag on inode 537613003 clearing reflink flag on inode 537613006 clearing reflink flag on inode 537613007 clearing reflink flag on inode 537613008 clearing reflink flag on inode 537613009 clearing reflink flag on inode 537613011 clearing reflink flag on inode 537613012 clearing reflink flag on inode 537613014 clearing reflink flag on inode 537613015 clearing reflink flag on inode 537613017 clearing reflink flag on inode 537613019 clearing reflink flag on inode 537613020 clearing reflink flag on inode 537613021 clearing reflink flag on inode 537613022 clearing reflink flag on inode 537613024 clearing reflink flag on inode 537613025 clearing reflink flag on inode 537613026 clearing reflink flag on inode 537613027 clearing reflink flag on inode 537613028 clearing reflink flag on inode 537613029 clearing reflink flag on inode 537613030 clearing reflink flag on inode 537613031 clearing reflink flag on inode 537613032 clearing reflink flag on inode 537613033 clearing reflink flag on inode 537613034 clearing reflink flag on inode 537613035 clearing reflink flag on inode 537613036 clearing reflink flag on inode 537613037 clearing reflink flag on inode 537613038 clearing reflink flag on inode 537613039 clearing reflink flag on inode 537613040 clearing reflink flag on inode 537613041 clearing reflink flag on inode 537613042 clearing reflink flag on inode 537613043 clearing reflink flag on inode 537613044 clearing reflink flag on inode 537613045 clearing reflink flag on inode 537613046 clearing reflink flag on inode 537613050 clearing reflink flag on inode 537613051 clearing reflink flag on inode 537613052 clearing reflink flag on inode 537613053 clearing reflink flag on inode 537613054 clearing reflink flag on inode 537613055 clearing reflink flag on inode 537615872 clearing reflink flag on inode 537615874 clearing reflink flag on inode 537615881 clearing reflink flag on inode 537615883 clearing reflink flag on inode 537615887 clearing reflink flag on inode 537615891 clearing reflink flag on inode 537615899 clearing reflink flag on inode 537615900 clearing reflink flag on inode 537615903 clearing reflink flag on inode 537615905 clearing reflink flag on inode 537615909 clearing reflink flag on inode 537615913 clearing reflink flag on inode 537615914 clearing reflink flag on inode 537615917 clearing reflink flag on inode 537615918 clearing reflink flag on inode 537615921 clearing reflink flag on inode 537615923 clearing reflink flag on inode 275214333 clearing reflink flag on inode 537615925 clearing reflink flag on inode 537615926 clearing reflink flag on inode 11514136 clearing reflink flag on inode 537615929 clearing reflink flag on inode 537615932 clearing reflink flag on inode 537615933 clearing reflink flag on inode 537615934 clearing reflink flag on inode 537615935 clearing reflink flag on inode 537643906 clearing reflink flag on inode 537643907 clearing reflink flag on inode 537643910 clearing reflink flag on inode 537643911 clearing reflink flag on inode 537643912 clearing reflink flag on inode 537643913 clearing reflink flag on inode 537643914 clearing reflink flag on inode 537643915 clearing reflink flag on inode 537643917 clearing reflink flag on inode 537643918 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - 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 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Sun May 22 08:46:33 2022 Phase Start End Duration Phase 1: 05/22 08:46:30 05/22 08:46:30 Phase 2: 05/22 08:46:30 05/22 08:46:30 Phase 3: 05/22 08:46:30 05/22 08:46:32 2 seconds Phase 4: 05/22 08:46:32 05/22 08:46:32 Phase 5: 05/22 08:46:32 05/22 08:46:32 Phase 6: 05/22 08:46:32 05/22 08:46:33 1 second Phase 7: 05/22 08:46:33 05/22 08:46:33 Total run time: 3 seconds done Quote Link to comment
mattekure Posted May 22, 2022 Author Share Posted May 22, 2022 what is the recommended filesys for pool devices? Should I convert over to btrfs? Quote Link to comment
itimpi Posted May 22, 2022 Share Posted May 22, 2022 31 minutes ago, mattekure said: what is the recommended filesys for pool devices? Should I convert over to btrfs? If you have a single device pool the XFS seems to be more stable. If you have a multi-device pool then btrfs is your only option. 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.