© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
No, I don't think it's an e2fsprogs issue. It looks like it's an init scripts issue. Fsck should always run on boot, regardless of whether or not /forcefsck is set. What forcefsck should do is set the -f flag, to request a forced check even though the file system appears clean.