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 [email protected] 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
>
> 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.
...
> whenever it does happen. It is wrong to think this problem happens
> only with Seagate drives.
indeed, it seems that the most common trigger for this problem
is simply putting two devices from different vendors on the same channel.
Seagate drives are fairly notorious for not getting along with others.
it's best to think of IDE as a point-to-point link.
regards, mark hahn.
------------------------------------------------------------------
Steven C. Timm (630) 840-8525 [email protected] http://home.fnal.gov/~timm/
Fermilab Computing Division/Operating Systems Support
Scientific Computing Support Group--Computing Farms Operations
On Mon, 1 Oct 2001, Mark Hahn wrote:
> > 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.
> ...
> > whenever it does happen. It is wrong to think this problem happens
> > only with Seagate drives.
>
> indeed, it seems that the most common trigger for this problem
> is simply putting two devices from different vendors on the same channel.
> Seagate drives are fairly notorious for not getting along with others.
>
> it's best to think of IDE as a point-to-point link.
True... however, we were still able to reproduce these problems
with only one drive on the bus.
Steve
>
> regards, mark hahn.
>
>