continued ext2fs corruption
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Rob Todd
I am using RH 7.1 with the stock 2.4.2-2 kernel (although the same behavior shows up in 2.4.4 also compiled using gcc 2.96). Not quite sure about hardware we share... it is a 1GHz P3 ServerWorks LE board (with the OSB4 chipset) connecting to a Seagate ST320414A 20GB HD (UDMA 33). We have several hundred other machines (including older ServerWorks boards) running 2.4.4 with no problem so I was extremely surprised to receive these 32 machines and have every single one of them experience some sort of file system corruption. I am running 2.2.19 right now on these 32 machines with no problems whatsoever.
Quoted 3 lines
Quoted 2 lines · Rob Todd
If you receive an answer please let me know... I've been seeing the same problems on a 1GHz P3 with a ServerWorks OSB4 chipset.
on the surface, it looks like your systems don't have anything in common with mine. i'm running rh71 too, but that's only because running kernel 2.4.2 on my previous rh62 system corrupted the filesystem so badly that i had to format and reinstall. i admit i'm somewhat glad to hear i'm not the only one having these problems, but it obviously isn't particularly widespread. are you also getting errors like this:
EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory #508411: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
the disk that becomes corrupted for me is an IBM Deskstar (UDMA 33), and it's on an intel 440BX chipset. does anyone here have any thoughts?
thanks,
ian