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 [EMAIL PROTECTED] | www.FreeBSD.org _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
