[lkml]   [2002]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.17 oops - ext2/ext3 fs corruption (?)
Eric wrote:
> I seem to be having a reoccurring problem with my Red Hat 7.2 system
> running kernel 2.4.17. Four times now, I have seen the kernel generate an
> oops. After the oops, I find that one of file systems is no longer sane.
> The effect that I see is a Segmentation Fault when things like ls or du
> some directory (the directory is never the same). Also, when the system
> is going down for a reboot, it is unable to umount the file system. The
> umount command returns a "bad lseek" error.
> The first time this happened, it resulted in catastrophic corruption of
> /usr and I had to reinstall. At this time, /usr was an ext2 file system.
> When I reinstalled, I took the opportunity to reformat all the file
> systems, except /home, as ext3.

Everything here points at failing hardware. Probably memory errors.
People say that memtest86 is good at detecting these things. Another
way to verify this is to move the same setup onto a different computer...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:15    [W:0.088 / U:0.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site