[NTLUG:Discuss] sudden file system errors on boot

[Fred James]

Darin W. Smith wrote:

> It could be that the version of fsck.ext2 (what fsck calls if the 
> filesystem is ext2) in e2fsprogs (or whatever the package is called 
> these days) they are using in 7.3 is simply better able to detect bad 
> blocks than older versions & that you really do have bad blocks.
> 
> Or, it may be that the new version of e2fsprogs (if it is a different 
> version) erroneously reports bad blocks when you really have none.
> 
> I'd look out on rpmfind.net or on RH updates to see if there is a 
> newer version of the e2fsprogs.
> 
> That is, if you are using ext2.  If you are using reiserfs, you need 
> to be looking for reiserfsprogs, etc...
> 
RH 7.1 - kernel 2.4.2-2
RH 7.2 - kernel 2.4.7
RH 7.3 - kernel 2.4.18-3
File system: ext2 in all cases.

"man fsck.ext2" brings up man(ual) pages for e2fsck, which note the 
version as 1.27
"RPM" showed "e2fsprogs version 1.27-3" installed, but didn't give a 
specific versin for "e2fsck"
A search at RH for "e2fsck" finds version 1.27-9, but the notices on 
"Obsoletes" and "Conflicts" both said "None" - I am guessing the changes 
have to due with libraries in later versions of RH (i.e. 8.x and so on).

Still, shouldn't the file system be "clean" at least on the first boot 
(immediately after install)?