Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: error (nike.apache.org: local policy)
MIME-Version: 1.0
Date: Thu, 18 Apr 2013 14:17:38 +0200
Message-ID: 
 <CAKTVnOyj=ud1DFe-RDL8PZ_=eTcELvhxCCBrz-tGUzF5sttO0w@mail.gmail.com>
Subject: Corrupted database example file
From: Victor Nicollet <vnicollet@runorg.com>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=089e0111cf509da06804daa1963f

--089e0111cf509da06804daa1963f
Content-Type: text/plain; charset=UTF-8

Hello,

The @CouchDB twitter account thought you might find this information
helpful.

My SaaS start-up uses CouchDB as its primary database. Lately, I have been
having database corruption issues with version 1.2.0 : every few weeks, one
of our databases becomes corrupted, which has several negative consequences
(among others) :

   - Replication of that database fails (it does not even start).
   - Compaction of that database fails and *freezes* the server.
   - Several documents in the database become inaccessible through either
   direct access or through _all_docs.

 The latest affected database does not contain any information about our
customers, so I am allowed to release it publicly :

http://nicollet.net/public/2013-04-18.couchdb/prod-folder.couch

This database contains 325 irretrievable documents between identifiers
2xFEY0pU2Eb and 3Fn6l04G6Oa.
I hope this helps,

-- 
Victor Nicollet, CTO, www.runorg.com

--089e0111cf509da06804daa1963f--