From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id A2E6ABB81 for ; Fri, 18 Nov 2005 22:12:59 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAILCwqZ025043 for ; Fri, 18 Nov 2005 22:12:59 +0100 Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id WAA26053 for ; Fri, 18 Nov 2005 22:12:58 +0100 (MET) Received: from mail.enyo.de (mail.enyo.de [212.9.189.167]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAILCvZV025039 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 18 Nov 2005 22:12:58 +0100 Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by albireo.enyo.de with esmtp id 1EdDXR-0006cD-GQ; Fri, 18 Nov 2005 22:12:53 +0100 Received: from fw by deneb.enyo.de with local (Exim 4.54) id 1EdDXN-0002sS-7w; Fri, 18 Nov 2005 22:12:49 +0100 From: Florian Weimer To: Gerd Stolpmann Cc: Thomas Fischbacher , Oliver Bandel , caml-list@inria.fr Subject: Re: [Caml-list] [1/2 OT] Indexing (and mergeable Index-algorithms) References: <20051116234238.GA5741@first.in-berlin.de> <87r79fjxy4.fsf@mid.deneb.enyo.de> <1132325649.17170.1.camel@starlight> <20051118142244.GF1116@first.in-berlin.de> <87wtj6yqbw.fsf@mid.deneb.enyo.de> <87hdaayolx.fsf@mid.deneb.enyo.de> <1132344112.17483.9.camel@localhost.localdomain> Date: Fri, 18 Nov 2005 22:12:49 +0100 In-Reply-To: <1132344112.17483.9.camel@localhost.localdomain> (Gerd Stolpmann's message of "Fri, 18 Nov 2005 21:01:51 +0100") Message-ID: <877jb5slri.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at nez-perce with ID 437E43DA.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 437E43D9.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 indexing:01 gerd:01 stolpmann:01 kernel:01 kernel:01 data:02 data:02 florian:02 bugs:03 berkeley:03 generally:03 crashes:03 crashes:03 depends:04 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 * Gerd Stolpmann: >> All my crashes could be traced back to operator error and faulty >> hardware. Berkeley DB has a very bad reputation when it comes to data >> integrity and durability, but in my experience, this is simply not >> true. > > I think it is true. > > A good database must not become corrupt even if the hardware crashes. It depends on the crash. In my case, hardware flipped bits randomly under high load, eventually leading to a kernel crash. This is hard to correct in software. Generally, it's better to fix the broken hardware. I haven't lost data due to simple crashes yet (power outages, crash-early kernel bugs, or MCEs because of thermal issues -- knock on wood).