Re: FS Corruption
tony mancill wrote:
> On Sat, 28 Aug 1999, Hamish Moffatt wrote:
>
> > On Fri, Aug 27, 1999 at 11:13:16PM -0700, tony mancill wrote:
> > > I'm having the same problem, did some research, and there seems to be a
> > > problem with DMA for the VIA chipset. This jives well with the fact that
> >
> > Do you mean UltraDMA 33 (or 66)? I have one drive here which has that
> > and I haven't seen a problem with 2.2.10ac12, although since the UDMA
> > drive does not contain any linux partitions (only Windows) I might not
> > have noticed.
>
> UDMA 33. I've been hacking on it all night, and have found out that I can
> kill the filesystem everytime I use hdparm to turn DMA on, and cannot kill
> it if DMA is off. (I've been copying a slink source CD onto the drive and
> the doing "find . -exec cksum {} \;" on the contents. :) If DMA is on,
> nasty things start popping up in syslog almost immediately. Even when
> just reading from the fs (well, that involves modifying the atimes in the
> inodes), I experience data loss.
---snip---
> You probably wouldn't have Windows problems since most motherboard
> manufacturers include drivers for there IDE controller which fix crap like
> this. I checked the Soyo page, and they have one, even for my sorry
> motherboard.
>
> Anyway, sorry for the off-topic mail. Send me mail directly if you want
> any details about the problem.
>
---end quoted text---
Tony, I've had the same experience with my (crappy) Soyo motherboard and
DMA. I've learned the hard way to /not/ use hdparm and to /not/ enable
DMA support in new kernels. If you come across a fix, I'd love to hear
about it.
--
Regards,
Steve
Reply to: