From owner-freebsd-stable@FreeBSD.ORG Mon Nov 3 13:09:59 2003 Return-Path: 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 3A02816A4CE; Mon, 3 Nov 2003 13:09:59 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id F252043FA3; Mon, 3 Nov 2003 13:09:57 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hA3L8FYl001126; Mon, 3 Nov 2003 22:08:15 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hA3L8FZn001125; Mon, 3 Nov 2003 22:08:15 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200311032108.hA3L8FZn001125@spider.deepcore.dk> In-Reply-To: <20031103205817.GA30799@merlin.emma.line.org> To: Matthias Andree Date: Mon, 3 Nov 2003 22:08:14 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: jie@expertcity.com cc: freebsd-current@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 21:09:59 -0000 It seems Matthias Andree wrote: > 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? There are known issues with some Serverworks chips, but we need to now much more details on the HW to tell. the output of pciconf -l from the machine and the output from dmesg would be good starters. -Søren