2.5 oopses when dealing with bad blocks on scsi disk

[Helge Hafting]

One of my scsi disks has got some bad blocks.  
Accessing them (via ext2 on top of raid-0) usually results
in a wait and a io error. 

badblocks and e2fsck -l 
runs fine, but e2fsck -c causes oopses and
sometimes ends up shutting the disk down.  I've been unable
to capture any oops so far due to the several pages 
of output that follows.

This happens with 2.5.2dj2 (with ALSA).  Other
2.5 kernels I have also struggle with this.
Accessing the bad blocks through ext2 does not
update the bad block inode, I thought it should.

I plan on moving data to another disk and
replace the faulty one later.  I can run experiments
on the bad one if the fs/driver people here
wants more information.

The disks are 2 quantum atlas IV, connected to
a tekram adapter using the SYM53C8XX v. 2 driver.
Both disks have several partitions, some used
in raid-0.  

Helge Hafting