From owner-freebsd-current@FreeBSD.ORG Sat May 10 15:03:48 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 A582737B404 for ; Sat, 10 May 2003 15:03:48 -0700 (PDT) Received: from MX2.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67CE543F75 for ; Sat, 10 May 2003 15:03:47 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-32-7-dsl.mus.estpak.ee [80.235.32.7]) by MX2.estpak.ee (Postfix) with ESMTP id 32C1673621; Sun, 11 May 2003 01:02:10 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h4AF3jxW023054; Sat, 10 May 2003 18:03:45 +0300 (EEST) (envelope-from vallo) Date: Sat, 10 May 2003 18:03:44 +0300 From: Vallo Kallaste To: Heiko Schaefer Message-ID: <20030510150344.GA22618@kevad.internal> References: <3EBC6C6A.1040602@myrealbox.com> <20030510130934.R93229@daneel.foundation.hs> <20030510203854.E93229@daneel.foundation.hs> <3EBD50D7.88A78B48@mindspring.com> <20030510230658.R93229@daneel.foundation.hs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030510230658.R93229@daneel.foundation.hs> User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-current@freebsd.org Subject: Re: thanks, was: Re: data corruption with DISABLE_PSE+DISABLE_PG_G: unrelated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee 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 May 2003 22:03:49 -0000 On Sat, May 10, 2003 at 11:11:43PM +0200, Heiko Schaefer wrote: > > > what i am asking myself: > > > is there any chance that i still get any data corruption because of the > > > issues that you write about in some configuration ?! > > > > No. Not with thouse flags set. If you are getting data > > corruption with the flags set, then you have some other > > problem, most likely hardware. > > ok, that's the answer i was looking for - as solid as it can get, with > such issues, i guess :) Heiko, I'm not able to reproduce it on Dual Athlon 2400+ system with 1GB of ECC memory and two Hitachi 120GB disks. Created two ~90GB filesystems on both disks with plain newfs, no softupdates. Then ran the following to populate source filesystem: while :; do size=$(jot -nrw %dk 1 4000 7000); split -b ${size} $HOME/film/LOTR1.avi ${size}. ; done The source filesystem has ~45GB of data in ~7300 files. I used the following quick script to copy data and control the checksums. It's seventh run currently and no signs of corruption. I'll let it run through tomorrow just to be on the safe side. Seems like you have nasty hardware problem(s). #! /usr/local/bin/bash src="/opt/TESTDIR" dst="/opt1/TESTDIR" for ((i=0;i<10;i++)); do for dir in 1 2; do find ${src} -type f -print0 | xargs -0 -J % cp % ${dst}/${dir} done for dir in 1 2; do cd ${dst}/${dir} && \ find -s . -type f -print0 | xargs -0 md5 -r \ > ${HOME}/result${dir}.txt done for dir in 1 2; do cmp ${HOME}/result${dir}.txt ${HOME}/checksum.txt done find ${dst}/{1,2} -type f -print0 | xargs -0 rm done -- Vallo Kallaste