Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CABvT1DF09qBkVRBVtrFfUo=MM1cRQB8wuQdUDkbphcg5asUYqA@mail.gmail.com>
References: 
 <CAFov+BLaetda+GhCK_T4JOwAMONCWcRnDQPknAfjs7MiL044Dg@mail.gmail.com>
	<CABvT1DF09qBkVRBVtrFfUo=MM1cRQB8wuQdUDkbphcg5asUYqA@mail.gmail.com>
Date: Sat, 22 Sep 2012 14:46:02 +0200
Message-ID: 
 <CAFov+BJuUiaa2-9tpbuehm_ZeXkk2RHsbMHvVEVFj6_AZMPpTw@mail.gmail.com>
Subject: Re: recovering data from an unfinished compaction db
From: =?ISO-8859-2?Q?Rudi_Benkovi=E8?= <rudib@whiletrue.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

CouchDB doesn't recognize it. It's probably corrupted because the
partition ran out of free space during compaction itself. Does CouchDB
try to find a valid root node by reading the DB file from the tail and
skipping over "random" binary data? In that case I might just have to
let it run for some time before it finds it.

--Rudi

On Sat, Sep 22, 2012 at 2:40 PM, Robert Newson <rnewson@apache.org> wrote:
> The compacted file is a valid couchdb database, it should not be
> "corrupted", simply rename it to .couch.
>
> Obviously you will have lost any data that didn't make it over to the
> .compact file from the original .couch file that you have mistakenly
> deleted.
>
> B.
>
> On 22 September 2012 10:56, Rudi Benkovi=C4=8D <rudib@whiletrue.com> wrot=
e:
>> Hi,
>>
>> I have a .couch file where compaction hasn't finished its job and
>> we've lost the pre-compaction production DB file (an unfortunate
>> sysadmin error). Running CouchDB 1.2.0, so the new, corrupted file is
>> in disk format version 6, with snappy compression.
>>
>> I've tried using recover-couchdb
>> (https://github.com/jhs/recover-couchdb), but it crashes with the
>> message that disk format 6 isn't supported. I've also tried dropping
>> in 1.2.0 sources, but that also didn't work.
>>
>> Anyway, any hints on how to recover the data? 180GB file, lots of attach=
ments.
>>
>> Many thanks!
>>
>> --Rudi