Date: Mon, 3 Nov 2003 22:08:14 +0100 (CET) From: Soren Schmidt <sos@spider.deepcore.dk> To: Matthias Andree <matthias.andree@gmx.de> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: HELP: ServerWorks data corruption after 350 MB with BerkeleyDB 4.0? Message-ID: <200311032108.hA3L8FZn001125@spider.deepcore.dk> In-Reply-To: <20031103205817.GA30799@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311032108.hA3L8FZn001125>