From owner-freebsd-stable@FreeBSD.ORG  Mon Nov  3 12:58:21 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B3D4616A4CF; Mon,  3 Nov 2003 12:58:21 -0800 (PST)
Received: from mail.dt.e-technik.uni-dortmund.de
	(mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6284E43FD7; Mon,  3 Nov 2003 12:58:20 -0800 (PST)
	(envelope-from matthias.andree@gmx.de)
Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de
	[129.217.163.1])6428C12C78;	Mon,  3 Nov 2003 21:58:19 +0100 (CET)
Received: by merlin.emma.line.org (Postfix, from userid 500)
	id B8B4D99A4D; Mon,  3 Nov 2003 21:58:17 +0100 (CET)
Date: Mon, 3 Nov 2003 21:58:17 +0100
From: Matthias Andree <matthias.andree@gmx.de>
To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org
Message-ID: <20031103205817.GA30799@merlin.emma.line.org>
Mail-Followup-To: freebsd-stable@freebsd.org,
	freebsd-current@freebsd.org, jie@expertcity.com, ansh@expertcity.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
cc: jie@expertcity.com
cc: ansh@expertcity.com
Subject: HELP: ServerWorks data corruption after 350 MB with BerkeleyDB 4.0?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2003 20:58:21 -0000

Hi,

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?

Thanks in advance,

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95