From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.92.18 with SMTP id p18cs134209agb; Tue, 6 Oct 2009 05:41:18 -0700 (PDT) Received: by 10.224.86.134 with SMTP id s6mr1207269qal.63.1254832877060; Tue, 06 Oct 2009 05:41:17 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 39si1141544qyk.16.2009.10.06.05.41.16; Tue, 06 Oct 2009 05:41:17 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id A62E41858268; Tue, 6 Oct 2009 08:41:15 -0400 (EDT) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by rubyforge.org (Postfix) with ESMTP id 75C1415B8029 for ; Tue, 6 Oct 2009 08:40:55 -0400 (EDT) Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mv9LW-00066G-Sx for sup-talk@rubyforge.org; Tue, 06 Oct 2009 14:40:51 +0200 Received: from host-87-74-72-74.dslgb.com ([87.74.72.74]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Oct 2009 14:40:50 +0200 Received: from olly by host-87-74-72-74.dslgb.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Oct 2009 14:40:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: sup-talk@rubyforge.org From: Olly Betts Date: Tue, 6 Oct 2009 12:40:25 +0000 (UTC) Message-ID: References: <1e5fdab70910031304g255a9d13v4dc99400def375a5@mail.gmail.com> <1254600926-sup-5190@zyrg.net> <1e5fdab70910031406x713fad49ubb42b42463899c87@mail.gmail.com> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 87.74.74.72 (Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.14) Gecko/2009090217 Ubuntu/9.04 (jaunty) Firefox/3.0.14) Subject: Re: [sup-talk] Crash, bad index, and ensuing misery X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Guillaume Quintard writes: > On Sat, Oct 3, 2009 at 10:17 PM, Rich Lane club.cc.cmu.edu> wrote: > > I'd hoped this kind of corruption wouldn't be possible with newer > > xapian-index versions. What sup commit are you on? What version of > > Xapian are you using? Which Xapian backend, Flint or Chert? > > ubuntu 9.10 > libxapian-ruby1.8 1.0.14-1 > I'd say flink since I often have to remove flintlock after sup > commiting suicide. NEVER EVER remove the flintlock file. It's not the presence of the file which determines the lock, but rather whether there's an fcntl() lock on it, so removing it smashes any lock which is currently held, but leaves the process which held it thinking it still has exclusive write access to the database, which will likely quickly lead to a corrupt database, especially if you're doing so because Xapian says the database is already locked. If Xapian says that, then there really is a process which still has the database open for writing. My guess is that removing the flintlock file is the cause of the corruption you're seeing. Can you reproduce it on a database where you haven't removed this file? Also, both chert and flint use the same locking approach with a file called flintlock, so that doesn't discriminate between them. The easy way to tell which you have is whether there's a file called "iamflint" or "iamchert" in the database directory. Cheers, Olly _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk