From owner-freebsd-stable Mon Oct 1 11:13:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from weenix.guru.org (weenix.guru.org [24.163.46.66]) by hub.freebsd.org (Postfix) with ESMTP id 785E237B403 for ; Mon, 1 Oct 2001 11:11:32 -0700 (PDT) Received: by weenix.guru.org (Postfix, from userid 3002) id C693F25; Mon, 1 Oct 2001 14:11:27 -0400 (EDT) Date: Mon, 1 Oct 2001 14:11:27 -0400 From: Keith Mitchell To: Chris Dillon Cc: freebsd-stable@freebsd.org Subject: Re: fs corruption (ATA / 4.4-REL) Message-ID: <20011001141127.A4415@weenix.guru.org> References: <20010929080038.A16272@weenix.guru.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Mon, Oct 01, 2001 at 12:11:50PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The VIA chipset is probably your culprit, though I'm not exactly sure > if the MVP3 has the PCI bus corruption problem or if it is only the > later KT133/KT266 chipsets. If so, your motherboard vendor is > supposed to fix the PCI bus corruption problems in the BIOS, so try a > BIOS update. If that doesn't fix it, you'll have to install > 4.4-STABLE, since Soren just recently put a fix into the ata driver to > work around a problem with those chipsets that the motherboard vendors > should be fixing but aren't. That only affects DMA, right? I'm going to try and install with hw.ata.wc=0 hw.ata.ata_dma=0 hw.ata.atapi_dma=0 And see if that works. I don't see any of the IDMA errors that other people are reporting (maybe because I'm only uses UDMA33 and not UDMA66/100). All I see is data and/or filesystem corruption. Sometimes the fs gets blaster beyond repair, other times I see files get merged together, etc. A pain in the butt. -- Keith Mitchell Email: kmitch@guru.org PGP key available upon request To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message