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 of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.