lkml.org 
[lkml]   [2001]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: linux-2.4.0 scsi problems on NetFinity servers
From
Date
Ok, on a suggestion from JP, I've built the 2.4.0 kernel without SMP
support. I did, however, have to make one change to a header file to get
it to compile the kernel and here is a diff

diff include/linux/linux/kernel_stat.h include/linux/linux/kernel_stat.h.sv
48d47
< #ifdef CONFIG_SMP
50d48
< #endif

The code was only for stats, but did not have the appropriate wrapper
around a for-loop clause to access an SMP only variable.

So, with SMP support off, I started my tests and then headed home for the
evening. This morning when I arrived, I found my machine had crashed on
the 2nd run of my copy test, but with a little bit of a different crash.
First I'm getting multiple messages of the type

I/O error: dev 08:01

and then I'm getting messages of the type

EXT2-fs error (device sd(8,1)): read_inode_bitmap: Cannot read inode bitmap
- block_group = 34, inode_bitmap = 1114113
EXT2-fs error (device sd(8,1)): ext2_write_inode: unable to read inode
block - inode=229832, block=458756

where the numbers for the inodes, blocks, bitmaps, and groups vary; also
attempting to run any process in my root tty (even just reboot) results in
a segv and the I/O error messages some more (of note, the only filesystem
that gets trashed, ever, is the one with the test running on it, the root
partition is separate and never is affected, nor is any other partition).
So, although SMP may aggrevate the situation, it is not, apparently, the
cause of the problem.

BTW: this test case basically destroys my test filesystem such that I've
taken to creating a new fs on the partition each time - I tried fixing it
twice with fsck, and after 2 days it had still not completed the fixup in
each case.

thanks

kenbo

______________________
Firebirds rule, `stangs serve!

Kenneth "kenbo" Brunsen
Iris Associates

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

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