From owner-freebsd-current  Fri Dec  8 17:14:39 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec  8 17:14:37 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by hub.freebsd.org (Postfix) with ESMTP
	id 803A037B400; Fri,  8 Dec 2000 17:14:37 -0800 (PST)
Received: from sunfin.Finland.Sun.COM ([129.159.101.10])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA06263;
	Fri, 8 Dec 2000 17:14:35 -0800 (PST)
Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87])
	by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id DAA24617;
	Sat, 9 Dec 2000 03:14:32 +0200 (EET)
Received: (from tomppa@localhost)
	by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id DAA00975;
	Sat, 9 Dec 2000 03:14:31 +0200 (EET)
From: Tomi Vainio - Sun Finland - <Tomi.Vainio@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14897.34679.98975.812334@ultrahot.Finland.Sun.COM>
Date: Sat, 9 Dec 2000 03:14:31 +0200
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: ffs_valloc: dup alloc panics with stable/current 
In-Reply-To: <200012090044.eB90i9F03062@mass.osd.bsdi.com>
References: <14897.28646.3200.459030@ultrahot.Finland.Sun.COM>
	<200012090044.eB90i9F03062@mass.osd.bsdi.com>
X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: Tomi.Vainio@Sun.COM
Sender: Tomi.Vainio@finland.sun.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith writes:
 > > First motherboard we tried was Intel PPro 200Mhz (FX440 based I
 > > think/Natoma?).  Second one is newer 633MHz Celeron system but I don't
 > > know manufacturer.
 > 
 > But the same symptoms?  Have you tried replacing the controller (or even 
 > just the onboard RAM)?  
 >
All but raid controller was replaced (RAM, video, net).  We also have
another raid controller and we are going to test it also.  Also tried
with and without soft updates and async io.

 > 
 > But no other errors?  In particular, nothing that looks like a "real" I/O 
 > error?
 >
This we have to double check because normally we don't stare at the
console when we test this system.

 > The problem that you're seeing looks like filesystem metadata corruption. 
 > If it's not memory/system related, it has to be in the datapath from the 
 > disks through the driver.  I'm not aware of any bugs in the driver that 
 > could cause this. 8(
 > 
I think old PPro system even supported ECC memory.  We are getting out
ideas.  Maybe small 3 disk raid5 with little newer disks than we use
now.

  Tomppa
-- 
SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland
Tomi Vainio (System Support Engineer)     +358 9 52556300 hotline
email: Tomi.Vainio@Sun.COM                +358 9 52556252 fax


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message