Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 39340 invoked from network); 28 Oct 2008 14:41:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Oct 2008 14:41:19 -0000 Received: (qmail 24802 invoked by uid 500); 28 Oct 2008 14:41:23 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 24769 invoked by uid 500); 28 Oct 2008 14:41:23 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 24751 invoked by uid 99); 28 Oct 2008 14:41:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2008 07:41:23 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [69.145.82.195] (HELO skunk.mtbrook.bozemanpass.com) (69.145.82.195) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2008 14:40:10 +0000 Received: from [69.145.82.239] (unknown [69.145.82.239]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skunk.mtbrook.bozemanpass.com (Postfix) with ESMTP id 83028558265 for ; Tue, 28 Oct 2008 07:40:48 -0700 (PDT) Message-ID: <49072462.7090101@bozemanpass.com> Date: Tue, 28 Oct 2008 07:40:34 -0700 From: David Boreham User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Usage of JDBM : Experience feedbacks References: <4907233A.6080300@symas.com> In-Reply-To: <4907233A.6080300@symas.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Howard Chu wrote: > I find that quite difficult to believe. On a properly configured > installation we never see corruption or data loss. We've even tested > on machines that crashed due to failing DRAMs and the database > (containing over 1 terabyte of data) still recovered in under 2 > minutes on the subsequent reboot (after replacement of bad memory). +1 on that.