https://bugzilla.kernel.org/show_bug.cgi?id=217769 --- Comment #2 from Mariusz Gronczewski (xani666@xxxxxxxxx) --- It did, thanks for help! Why is that reported as "corruption of in-memory data" ? The filesystem on other machine also had exactly 3 disconnected inodes Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... agi unlinked bucket 0 is 559936 in ag 2 (inode=34114368) agi unlinked bucket 42 is 175466 in ag 2 (inode=33729898) agi unlinked bucket 53 is 198581 in ag 2 (inode=33753013) - 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 ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 33729898, would move to lost+found disconnected inode 33753013, would move to lost+found disconnected inode 34114368, would move to lost+found Phase 7 - verify link counts... -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
