From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: akpm@digeo.com, green@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: reiserfs oops [2.5.65]
Date: Thu, 20 Mar 2003 15:34:27 -0800 [thread overview]
Message-ID: <20030320153427.6265e864.rddunlap@osdl.org> (raw)
In-Reply-To: <20030320231335.GB4638@suse.de>
On Thu, 20 Mar 2003 23:13:35 +0000 Dave Jones <davej@codemonkey.org.uk> wrote:
| On Thu, Mar 20, 2003 at 04:59:41PM -0800, Andrew Morton wrote:
| > >
| > > Slab corruption: start=c70c7044, expend=c70c7213 problemat=c70c7044
| > > Last user: [<c0280dcb>](reiserfs_alloc_inode+0x1b/0x30)
| > > Data: (lots of hex)
| >
| > Alas, the "(lots of hex)" is important - it lets us determine which member of
| > struct reiserfs_inode was actually altered.
|
| You're in luck, as noted in the follow up, I captured it all..
| http://www.codemonkey.org.uk/cruft/oops.txt
|
| > It would be nice if we had a more robust way of capturing all this info,
| > especially the oops-while-running-X lossage. Dump-to-floppy or something.
|
| The tricky thing about capturing this one was that something in the VFS
| was wedged hard, so I'm lucky the logs made it to disk.
| Using sysrq, I synced and the disks made really nasty chugging noises.
| umount read only made it write a bunch of stuff out, more chugging
| noises for 15 minutes, kill all tasks then popped up a getty for me to
| log in on. It took about 3 minutes to get a shell (disk IO was seriously
| slow). I took a peek at vmstat 1 (no logs of this sorry), and nothing
| out of the ordinary. Not much in swap, plenty of swap free.
| short: the machine was horked. I synced, and rebooted, and thankfully
| the logs were still there after fsck.ext2 recovered /var
I've done some 2.5.xyz work on kmsgdump (dump kernel messages to
floppy). I'll try to get back to it soon.
--
~Randy
next prev parent reply other threads:[~2003-03-20 23:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 14:10 Dave Jones
2003-03-20 8:25 ` Oleg Drokin
2003-03-20 11:48 ` Dave Jones
2003-03-20 13:24 ` Dave Jones
2003-03-20 14:03 ` Dave Jones
2003-03-21 0:59 ` Andrew Morton
2003-03-20 23:13 ` Dave Jones
2003-03-20 23:34 ` Randy.Dunlap [this message]
2003-03-22 19:36 ` Nicholas Wourms
2003-03-25 16:15 ` Bill Davidsen
2003-03-31 18:53 ` [announce] kmsgdump for 2.5.65/66 Randy.Dunlap
2003-03-31 19:17 ` Nicholas Wourms
2003-03-31 20:44 ` Randy.Dunlap
2003-03-21 9:14 ` reiserfs oops [2.5.65] Oleg Drokin
2003-03-21 11:54 ` Dave Jones
2003-03-21 13:42 ` Oleg Drokin
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=20030320153427.6265e864.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=green@namesys.com \
--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®