https://bugzilla.kernel.org/show_bug.cgi?id=217769 --- Comment #3 from Eric Sandeen (sandeen@xxxxxxxxxxx) --- It's essentially an unexpected/inconsistent in-memory state, as opposed to an on-disk structure that was found to be corrupt. I presume that it boots ok now post-repair? Do you know if this was the root or /boot filesystem or something else? It's still a mystery about how filesystems get into this state; we should never have a clean filesystem that requires no log recovery, but with unlinked inodes ... recovery is supposed to clear that. It may have persisted on this filesystem for a very long time and it's just recent code changes that have started tripping over it, but I've always had a hunch that /boot seems to show the problem more often. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
