December 20, 20241 yr I don't monitor my system very often so I'm not sure how long it's been like this, but I happened to login the other day and found disk 1 unmountable. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - 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 - 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 = 7 - agno = 3 - agno = 6 - agno = 1 - 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... Maximum metadata LSN (3:83707) is ahead of log (3:80876). Would format log to cycle 6. No modify flag set, skipping filesystem flush and exiting. wolbaznas-diagnostics-20241219-1947.zip
December 20, 20241 yr Community Expert Solution You need to run without -n or no repair will be done, and if it ask for it add -L.
December 20, 20241 yr Author Okay I wasn't sure if I should remove the flag without asking about the messages here first.
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.