[
https://issues.apache.org/jira/browse/COUCHDB-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896238#action_12896238
]
Sascha Reuter commented on COUCHDB-844:
---------------------------------------
Hi Damien,
filesystem is ext3 and I'm using LVM. Filesystem corruption is rather unlikely
and space was always plenty available (about 50%usage)...
As said before, i just restarted the CouchDB via the provided init script.
Let me know if you need any more information on this!
Cheers,
Sascha
> Documents missing after CouchDB restart
> ---------------------------------------
>
> Key: COUCHDB-844
> URL: https://issues.apache.org/jira/browse/COUCHDB-844
> 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 (/var/lib/couchdb/<database>.couch)
> 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.
