Why does force fsck generate/move so many files to "lost+found" even in an empty filesystem?
Issue
- Why does force fsck generate/move so many files to "lost+found" even in an empty filesystem?
Environment
- Red Hat Enterprise Linux 5
- EXT3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
