Re: kernel debugger and Infortrend and bad blocks

[Joe Kaiser <jlkaiser@xxxxxxxx>]

This is what I got on boot up:

Mounting local filesystems:
Entering kdb (current=0xc03a6000, pid 0) on processor 0 due to
NonMaskable Interrupt @ 0xc0107098
eax = 0x00000000 ebx = 0xc0107070 ecx = 0x00000000 edx = 0xc03a6000
esi = 0xc03a6000 edi = 0xc03a6000 esp = 0xc03a7fc0 eip = 0xc0107098
ebp = 0xc0107070 xss = 0xc0270068 xcs = 0x00000060 eflags = 0x00000246
xds = 0x00000068 xes = 0xf7fe0068 origeax = 0x00000000 &regs =
0xc03a7f8c
[0]kdb> 
Catastrophic error detected
kdb_continue_catastrophic=1, attempting to continue

Thanks,

Joe

On Tue, 2004-02-24 at 18:08, Eric Sandeen wrote:
> Details please, what did the kernel say...  xfs knows nothing about bad
> blocks on the disk, but it does know about I/O errors.
> 
> -Eric
> 
> On Tue, 2004-02-24 at 17:27, Joe Kaiser wrote:
> > Hi,
> > 
> > I have a number of Infortrends that cause XFS to go into the kernel
> > debugger and unmount the XFS filesystem whenever a bad block is found on
> > the disk.  A remount and then a dismount and an xfs_repair is then
> > required to fix the problem.  Is there anyway to avoid this?  Why is XFS
> > even getting bad block information from the disk?
> > 
> > I am using XFS1.3.1 on 2.4.20-20.9.....
> > 
> > Thanks, 
> > 
> > Joe 
-- 
===================================================================
Joe Kaiser - Systems Administrator                

Fermi Lab 
CD/OSS-SCS                Never laugh at live dragons.
630-840-6444
jlkaiser@xxxxxxxx                                                
===================================================================