From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 13:01:46 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 DB1CE16A4CE for ; Mon, 3 Nov 2003 13:01:46 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59A8A43F3F for ; Mon, 3 Nov 2003 13:01:46 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 5198672DB5; Mon, 3 Nov 2003 13:01:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 4BE0272DB3; Mon, 3 Nov 2003 13:01:46 -0800 (PST) Date: Mon, 3 Nov 2003 13:01:46 -0800 (PST) From: Doug White To: Matthias Andree In-Reply-To: <20031103205817.GA30799@merlin.emma.line.org> Message-ID: <20031103130026.B86138@carver.gumbysoft.com> References: <20031103205817.GA30799@merlin.emma.line.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: HELP: ServerWorks data corruption after 350 MB with BerkeleyDB 4.0? 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: Mon, 03 Nov 2003 21:01:47 -0000 Don't crosspost -stable and -current. Thanks! On Mon, 3 Nov 2003, Matthias Andree wrote: > I received a bug report against BerkeleyDB 4 that may not be BerkeleyDB > related, but a problem with FreeBSD or specific hardware in general. > > Jie Song (CC'd) reported that writing files with BerkeleyDB (no > threading or something) on his ServerWorks machine causes data > corruption (detected by BerkeleyDB 4.0 library functions) when the file > sizes grow beyond 350 MB. For details, see PR #55252. Jie Song has > answered in private mail that the problem persists with both current 4.X > and current 5.X FreeBSD versions. > > Does this ring a bell somewhere? Are there issues with BIOS versions > usually used on ServerWorks boards, are there hardware > detection/configuration issues in the kernel? Anything known? If he is using the onboard ROSB4 IDE controller on LE-III chipsets, that IDE controller is known to cause data corruption if the disks are running in ATA33 mode. If he is using the ROSB4, demote to PIO or use a different controller. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org