* Nasty oops with 2.4.8
@ 2001-08-19 13:38 John Levon
0 siblings, 0 replies; only message in thread
From: John Levon @ 2001-08-19 13:38 UTC (permalink / raw)
To: linux-kernel
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 ...
john
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-08-19 13:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-19 13:38 Nasty oops with 2.4.8 John Levon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®