lkml.org 
[lkml]   [2001]   [Oct]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: DMA problem (?) w/2.4.6-xfs and ServerWorks OSB4 Chipset
As mentioned earlier on this list, we saw similar corruption,
detectable by the fact that if you do a ls -R on the file system
there will be input/output errors due to inodes that are no longer
there, eventually.
We began with a system with a Seagate system drive (master, ide0), same
model as in Marvin's post.. IDE cd rom
as slave on the ide0 bus, and two IBM data drives on the ide1 bus.

The vendor eventually swapped out all the Seagate drives for
Western Digital ones, which does not make the problem go away,
but makes it much less frequent and harder to reproduce, but
at least there is something in /var/log/messages to show for it
whenever it does happen. It is wrong to think this problem happens
only with Seagate drives.

Steve

------------------------------------------------------------------
Steven C. Timm (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/
Fermilab Computing Division/Operating Systems Support
Scientific Computing Support Group--Computing Farms Operations

On Sun, 30 Sep 2001, Alan Cox wrote:
>
> 1. Use multiword DMA not UDMA
> 2. Use non seagate disks with that controller
>
> I am hopeful that serverworks will figure out what is up, but not every box
> sees it - and indeed they've yet to be able to reproduce it.
>
>
> Alan
>

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

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