From owner-freebsd-current@FreeBSD.ORG Thu May 8 08:12:32 2003 Return-Path: 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 8719337B401 for ; Thu, 8 May 2003 08:12:32 -0700 (PDT) Received: from sauron.fto.de (p15106025.pureserver.info [217.160.140.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8711E43FBD for ; Thu, 8 May 2003 08:12:31 -0700 (PDT) (envelope-from hschaefer@fto.de) Received: from localhost (localhost.fto.de [127.0.0.1]) by sauron.fto.de (Postfix) with ESMTP id 20B7025C0F7; Thu, 8 May 2003 17:12:30 +0200 (CEST) Received: from sauron.fto.de ([127.0.0.1]) by localhost (sauron [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22163-07; Thu, 8 May 2003 17:12:28 +0200 (CEST) Received: from giskard.foundation.hs (p5091A984.dip.t-dialin.net [80.145.169.132]) by sauron.fto.de (Postfix) with ESMTP id 09CE025C0FA; Thu, 8 May 2003 17:12:27 +0200 (CEST) Received: from daneel.foundation.hs (daneel.foundation.hs [192.168.20.2]) by giskard.foundation.hs (8.9.3/8.9.3) with ESMTP id RAA64409; Thu, 8 May 2003 17:12:26 +0200 (CEST) (envelope-from hschaefer@fto.de) Date: Thu, 8 May 2003 17:12:26 +0200 (CEST) From: Heiko Schaefer X-X-Sender: heiko@daneel.foundation.hs To: Vallo Kallaste In-Reply-To: <20030508073911.GA4839@kevad.internal> Message-ID: <20030508170353.J79286@daneel.foundation.hs> References: <20030506162410.M66653@daneel.foundation.hs> <20030508155123.G78057@daneel.foundation.hs> <20030508073911.GA4839@kevad.internal> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at fto.de cc: current@freebsd.org Subject: Re: data corruption with current (maybe sis chipset related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 08 May 2003 15:12:32 -0000 Hello Vallo, > > > > options DISABLE_PSE > > > > options DISABLE_PG_G > > > > ok. i have done my copying and checksumming orgy with these options in the > > kernel - and it seems that i do not get any corruption anymore. > > i will re-run my test once again now, just to be safe. > > > > after that: does it make sense to single out which of the two options is > > the relevant one ? > > > > i'm also clueless what exactly these options do, and what exactly we've > > ruled out now. could the lack of data-corruption just be some side-effect? > > I'm also forced to use these options on my P4 workstation, otherwise > every parallel buildworld over -j4 gave me gcc internal errors. Can > you please give your testing procedure, as I have two 120GB ATA > disks and plenty of free space. The system I'll be testing on is > 2x2400+ MP system with 1G of ECC memory. here's what i do: i have one 30gb disk and one 60gb disk (both ide, one is udma66, the other udma100), i'll call them A and B. A is filled up with lots of files of approx 5mb size. i've had them checksummed in the beginning (i use 'cfv', which can be found in ports - but i'm sure any checksumming program will do the trick) i then copy all these files from A onto B ("cp -Rp"), twofold (into two subdirs), just to move a lot of data. sometimes i did that in parallel, sometimes serially - it doesn't seem to make any difference. then i let cfv test the checksums of the two copied directories on B. usually i got one or two checksum mismatches. occasionally in addition, the filesystem on B was damaged (i noticed this when 'wc' told me different size than ls -l for one of the mismatching files. fsck found something to repair in that case). regards, Heiko -- Free Software. Why put up with inferior code and antisocial corporations? http://www.gnu.org/philosophy/why-free.html