From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs212753vdc; Tue, 10 May 2011 23:37:25 -0700 (PDT) Received: by 10.52.100.70 with SMTP id ew6mr2924448vdb.95.1305095845465; Tue, 10 May 2011 23:37:25 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e9si6550691vcx.201.2011.05.10.23.37.24; Tue, 10 May 2011 23:37:24 -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; dkim=neutral (body hash did not verify) header.i=@pimlott.net Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3C20215B8029; Wed, 11 May 2011 02:37:24 -0400 (EDT) Received: from fugue.pimlott.net (pimlott.net [72.249.23.100]) by rubyforge.org (Postfix) with ESMTP id 0568218583A3 for ; Wed, 11 May 2011 02:14:41 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=pimlott.net; s=default; h=Content-Transfer-Encoding:Message-Id:Date:References:In-reply-to:To:From:Subject:Content-Type; bh=tKjFFnRn6nMG8X43dfI6YP2jPfp0nDkJJfjA2XxB+RI=; b=T2/He3dmZftbFjCsD4r9MGYGMhDvLWVEY9CM9tChF1krhypaHk22z8giHs+VU1pv4XwEVS4aeR8TVtGUfCMx8YVU9PKmU35WPLj3yk8UrMWm9gCFb3R3ntzOoX1/S1CJ+4B3DWEYprGP7AGY7lyal93jrSFjFqvf5TljFbFa/ZA=; Received: from andrew by fugue.pimlott.net with local (Exim 4.72) (envelope-from ) id 1QK2gL-00052l-Tl for sup-talk@rubyforge.org; Tue, 10 May 2011 23:14:02 -0700 From: Andrew Pimlott To: sup-talk In-reply-to: <1305074074-sup-8794@masanjin.net> References: <20110506220650.GA23223@pimlott.net> <1305074074-sup-8794@masanjin.net> Date: Tue, 10 May 2011 23:14:01 -0700 Message-Id: <1305093702-sup-3221@pimlott.net> User-Agent: Sup/git Subject: Re: [sup-talk] DatabaseCorruptError 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from William Morgan's message of Tue May 10 17:36:54 -0700 2011: > Reformatted excerpts from Andrew Pimlott's message of 2011-05-06: > > Sup had been running for a while, and I just came back to my terminal to > > find it dead: > > > > --- IOError from thread: periodic poll > > DatabaseError: Error reading block 4279173482: got end of file > > I'm running an old git pull from next, commit 1bafcf6 dated 2010-10-12. > > Yipes. Are you out of disk space, or anything like that? I wasn't out of space--unless possibly Xapian caused some transient spike in disk use that was freed when it died. The system does run without a ton of free space though, maybe 100 MB for a Xapian database that is ~300 MB total. I didn't get any disk errors either. This is on a VPS that could conceivably be hiding some errors. > > Anything I should do to try to diagnose and recover this? Or just > > load from sup-dump? > > Not knowing very much about Xapian, I suggest sup-dump. Not a great > solution, I know. It turned out that sup-dump still worked. Probably some index was corrupt but the data could still be walked. So I was able to restore without losing any data. (Well, it did use most of the 160 MB of memory on the VPS.) > Wait for heliotrope to solve your problems (or at > least be something I understand and can fix). Dum de dum dum... Andrew _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk