From owner-freebsd-current@FreeBSD.ORG Sat Sep 10 09:39:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BABE416A41F for ; Sat, 10 Sep 2005 09:39:03 +0000 (GMT) (envelope-from gregorynou@altern.org) Received: from esemetz.metz.supelec.fr (esemetz.metz.supelec.fr [193.48.224.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEBB843D48 for ; Sat, 10 Sep 2005 09:39:02 +0000 (GMT) (envelope-from gregorynou@altern.org) Received: from smtp.metz.supelec.fr (smtp.metz.supelec.fr [193.48.224.205]) by esemetz.metz.supelec.fr (8.11.6/8.9.3) with ESMTP id j8A9d2I12006 for ; Sat, 10 Sep 2005 11:39:02 +0200 Received: from [193.48.225.2] (nou.rez-metz.supelec.fr [193.48.225.2]) by smtp.metz.supelec.fr (8.11.6/8.11.6) with ESMTP id j8A9YfK00789; Sat, 10 Sep 2005 11:34:41 +0200 Message-ID: <4322A9AF.5000801@altern.org> Date: Sat, 10 Sep 2005 11:38:55 +0200 From: Gregory Nou User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: othermark References: <4316E1A0.8070307@altern.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Problem with deleting files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2005 09:39:03 -0000 othermark wrote: >Gregory Nou wrote: > > >>I'm currently experiencing a weird problem : some of my folders are >>completely empty (ls -a doesn't even mention . or ..) >>But, I cannot remove them, and a ls is very very slow (but just in those >>folders, and it is quite rare, but now I cannot update firefox, nor >>openoffice, because make clean will fail). >> >> > >Yeah, I've seen this. For me, this is the direct result of the ServerWorks >chipset on the box not properly doing DMA, and in fact causes corruption on >the bus when DMA is enabled for the IDE controller. Usually you see this >when doing large extracts or deletes (like the openoffice of >mozilla/firefox ports). You need to fsck, hopefully before you even read >this (you'll see lots of softupdate problems being fixed). > >You'll also notice that your daily automatic reports sent to root will >mention problems with traversing files or directories. > >For reference this bad boy: > >atapci0: port >0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc90-0xfc9f at device 15.1 on pci0 > >atapci0@pci0:15:1: class=0x01018a card=0x00000000 chip=0x02111166 >rev=0x00 >hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'OSB4 PCI EIDE Controller' > class = mass storage > subclass = ATA > >The only solution is to run with dma off (see atacontrol, or shut it off in >BIOS). > > > Thanks for the answer. However, I did not have the chance to test it, because I had the very bad idea to reboot. I tried to fsck and had lots of : ad2: FAILURE - READ_DMA status=51 error=40 LBA=xxxxxxx So the system was marked as dirty, and I could not boot. I just could backup datas and reinstall all. making a newfs on the damaged slice made the errors disppear. I suppose it's normal. But I cannot understand why fsck was unable to correct it, because it asked me if I wanted to correct, but told me then that it could not write on this sector. That's weird . -- Gregory