couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damien Katz (JIRA)" <>
Subject [jira] Commented: (COUCHDB-844) Documents missing after CouchDB restart
Date Sat, 07 Aug 2010 01:18:16 GMT


Damien Katz commented on COUCHDB-844:

Hello Sascha.

What file system are you running? Can you run a consistency check on it?

It's strange. It looks like your file was either truncated or the header was never written.
There is a bunch of data after the last header, and it contains your missing data, but none
of it looks like a header for it. All the interval markers are set for data. This is consistent
with a file that's been truncated. Still doing a bit more investigation to check the data
regions to see if they might actually have a header.

We have seen instances in the past (0.8.0 and earlier) where file systems have truncated the
db file, making recovery difficult, which is why we switched to pure tail append format. As
I recall, those reports were associated with the file system running out of space.

Barring a physical corruption or truncation, the other only possibility I can think of is
somehow there is bug where the couchdb isn't writing the header. I don't know of any other
instances of that happening, but if that's what it is, it's a very serious bug.

> Documents missing after CouchDB restart
> ---------------------------------------
>                 Key: COUCHDB-844
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 1.0
>         Environment: Debian Version 5.0.5, Linux *** 2.6.29-xs5.5.0.17 #1 SMP Mon Aug
3 17:37:37 UTC 2009 i686 GNU/Linux, XenServer Guest
>            Reporter: Sascha Reuter
>            Priority: Critical
> After a CouchDB restart, recently added/changed documents+designdocuments (min. 2 weeks
timeline!) are missing and cant be accessed trough REST Calls / Futon. 
> All documents that are still available trought REST/Futon only exist in old revisions.
> All documents/revisions can be found doing a manual search (less/egrep/...) in the datafile
> Example:
> strings dtap.couch | grep -i "226b2e6c-24b7-4336-92c7-257abf923b11"
> $226b2e6c-24b7-4336-92c7-257abf923b11h
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11l
> $226b2e6c-24b7-4336-92c7-257abf923b11h
> $226b2e6c-24b7-4336-92c7-257abf923b11h
> curl http://localhost:5984/dtap/226b2e6c-24b7-4336-92c7-257abf923b11
> {"error":"not_found","reason":"missing"}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message