From: John Levon <moz@compsoc.man.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Nasty oops with 2.4.8
Date: Sun, 19 Aug 2001 14:38:01 +0100 [thread overview]
Message-ID: <20010819143801.A90831@compsoc.man.ac.uk> (raw)
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
reply other threads:[~2001-08-19 13:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010819143801.A90831@compsoc.man.ac.uk \
--to=moz@compsoc.man.ac.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®