[lkml]   [2001]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectNasty oops with 2.4.8

I got an oops yesterday just after loggin in. The machine was idle.

Unfortunately the problem trashed a number of files on the root partition, including all
traces of the (decoded) oops.

I do remember it was a pointer dereference fault in sync_unlocked_inodes(), not a NULL pointer.

The machine passes memtest86 without a hitch, has been stable with 2.4.3 and earlier for ages. ext2 /,
UP Celery 600

Interestingly during the fsck an fsck.ext2 bug was uncovered where inode_link_info was 0 but
inode.i_links.count was 1 (no, I definitely wasn't fscking a rw / ;). Perhaps that is fixed
in 1.19 though, I was using 1.18

hope this helps someone debug this rather nasty FS corruption ...

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 12:57    [W:0.027 / U:1.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site