xfs
[Top] [All Lists]

Re: kernel debugger and Infortrend and bad blocks

To: Joe Kaiser <jlkaiser@xxxxxxxx>
Subject: Re: kernel debugger and Infortrend and bad blocks
From: James Pearson <james-p@xxxxxxxxxxxxxxxxxx>
Date: Wed, 25 Feb 2004 14:51:30 +0000
Cc: linux-xfs@xxxxxxxxxxx
Organization: Moving Picture Company
References: <1077665271.1051.21.camel@xxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
We had a look an Infortrend array (SATA internally, SCSI externally) and
had a lot of problems - it looked like problems in the array 'leaked'
through to the host - e.g. a failed disk caused the external SCSI bus to
reset etc.

Internal problems like this with the raid disks should be handled by the
raid controller - the host should be unaware of these problems.

Because of these problems, we rejected the Infortrend ...

James Pearson

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
> ===================================================================


<Prev in Thread] Current Thread [Next in Thread>