Maybe its a good idea to send out a warning or something. My guess is that other people affected by this problem just don't know, until they restart their instances... :-/ don't know...
Am 07.08.2010 um 20:15 schrieb Volker Mische <[email protected]>: > Damine, > > as you found already a suspicious commit, it might not be much help. But the > GeoCouch merge with 1.0 had also some issues, the original GeoCouch not, > which is based on a checkout around beginning of March. > > Cheers, > Volker > > On 08/07/2010 08:12 PM, Damien Katz wrote: >> SVN commit r954043 looks suspicious. Digging further. >> >> -Damien >> >> On Aug 7, 2010, at 10:31 AM, J Chris Anderson wrote: >> >>> >>> On Aug 7, 2010, at 1:21 AM, Sascha Reuter wrote: >>> >>>> Thats exactly what I reported 2 days ago! Bug is already opened and >>>> databasefile was provided to the couchio guys! Running on Linux... >>>> >>> >>> Thanks, we're keenly interested in seeing what's going on here. >>> >>> Chris >>> >>>> Am 07.08.2010 um 06:37 schrieb J Chris Anderson<[email protected]>: >>>> >>>>> >>>>> On Aug 6, 2010, at 9:02 PM, Yue Chuan Lim wrote: >>>>> >>>>>> Sorry to reply myself so quickly. >>>>>> >>>>>> Peeking inside the .couch file and searching for the documents I have >>>>>> missing turn up results. Offhand I am noticing 4 instances of the string >>>>>> gsc_test_03. Which is ID of the document I am missing. >>>>>> >>>>> >>>>> You are on Windows? Perhaps this is an issue with the windows file >>>>> handling. >>>>> >>>>> Can you comment on this bug, and also save those .couch files in case we >>>>> need to analyze them? >>>>> >>>>> Corruption like this should be impossible, but this is the second case >>>>> we've heard lately, so I'm guessing it is a Windows issue. >>>>> >>>>> Please comment on this bug with information about your machine enviroment >>>>> (OS, Filesystem, Disk size, etc) >>>>> >>>>> https://issues.apache.org/jira/browse/COUCHDB-844 >>>>> >>>>> Thanks! >>>>> >>>>> Chris >>>>> >>>>> >>>>> >>>>>> On Sat, Aug 7, 2010 at 11:58 AM, Yue Chuan Lim<[email protected]> >>>>>> wrote: >>>>>> >>>>>>> I have a set of documents that have been committed for more then a day, >>>>>>> regularly read from without a problem. Had to stop the database service >>>>>>> to >>>>>>> do some debugging, used the couchdb.bat provided in CouchDB/bin for easy >>>>>>> access to the log. And I noticed that I basically lost all the >>>>>>> documents in >>>>>>> question. >>>>>>> >>>>>>> There does not appear to be corruption per se, but it is as if my >>>>>>> database >>>>>>> just rolled back to the state it was in a few days ago, i.e. most of my >>>>>>> documents are there but some old documents that I'm pretty sure I have >>>>>>> deleted are back, and my newer documents are gone. >>>>>>> >>>>>>> Appears to have happened to me more then once, shrugged it off the last >>>>>>> time as it might be just a mix up, but I am definite that my database >>>>>>> has >>>>>>> certainly rolled back this time. >>>>>>> >>>>>>> Is there any situation in which this might happen? >>>>>>> >>>>>>> Thanks >>>>>>> Yue Chuan >>>>>>> >>>>> >>> >> >
