From owner-freebsd-hackers@FreeBSD.ORG Mon May 12 19:24:35 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13A4D106566C for ; Mon, 12 May 2008 19:24:35 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id 97F508FC16 for ; Mon, 12 May 2008 19:24:34 +0000 (UTC) (envelope-from mwm@mired.org) Received: (qmail 56465 invoked from network); 12 May 2008 15:25:00 -0400 Received: from unknown (HELO mbook.local) (192.168.195.193) by 0 with SMTP; 12 May 2008 15:25:00 -0400 Date: Mon, 12 May 2008 15:24:30 -0400 From: Mike Meyer To: Anthony Pankov Message-ID: <20080512152430.3720683e@mbook.local> In-Reply-To: <1663320218.20080512223531@mail.ru> References: <9FC19AC2-DAD8-418C-8B9C-F129DEC58CEF@gmail.com> <15336578.20080512123806@mail.ru> <200805121153.00809.jonathan+freebsd-hackers@hst.org.za> <1663320218.20080512223531@mail.ru> Organization: Meyer Consulting X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.2.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 12 May 2008 20:09:33 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: BDB corrupt X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 19:24:35 -0000 On Mon, 12 May 2008 22:35:31 +0400 Anthony Pankov wrote: > Because BDB: > 1. do not need additional installation > 2. is part of base system which mean it is mature, reliable and stable BDB in the base system is mature, reliable and stable *for what it's used for in the base system.* So long as your requirements are covered by that usage, you'll be ok. The uses I know of for BDB in the base system all consist of databases of relatively small items that are changed infrequently, and usually with a locking mechanism. From what you've said, this doesn't describe your requirements. More importantly, from what other people are saying, your requirements are ones for which it's known that BDB is *not* reliable, or otherwise unsuitable. In particular, an effort is underway to allow parallel ports builds, which implies concurrent access to the database, which is a known source of problems for BDB.