couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <paul.joseph.da...@gmail.com>
Subject Re: corrupted database file
Date Tue, 12 May 2009 23:54:15 GMT
On Tue, May 12, 2009 at 7:45 PM, Peter Hsu <phsu@abaca.com> wrote:
> May I ask where the feature lives in the timeline?
>

I don't have anything more specific than the next couple of months
probably. It really depends on when the first person decides to tackle
the patch.

HTH,
Paul Davis

> On May 12, 2009, at 3:52 PM, Paul Davis wrote:
>
>> On Tue, May 12, 2009 at 6:17 PM, Peter Hsu <phsu@abaca.com> wrote:
>>>
>>> What does "tail-append" headers mean?
>>>
>>> Is there anything that can be done in the current version to avoid this?
>>> (aside from ensuring there is always disk space)
>>>
>>
>> Its a planned feature so that instead of overwriting the header at the
>> beginning of the file we just append a new header to the end of the
>> file. In the future when you have a weird file truncation we can just
>> walk backwards through the db to get the last valid version assuming
>> there's no corruption in the middle of the file.
>>
>> HTH,
>> Paul Davis
>>
>>> Thanks,
>>> Peter
>>>
>>> On May 12, 2009, at 12:23 PM, Damien Katz wrote:
>>>
>>>> It looks like the database file got truncated. Until we get tail-
>>>> append headers, there is no way to recover the file contents when this
>>>> happens.
>>>>
>>>> -Damien
>>>>
>>>>
>>>> On May 12, 2009, at 1:25 PM, Peter Hsu wrote:
>>>>
>>>>> I get the following error when visiting futon:
>>>>>
>>>>> Database information could not be retrieved:
>>>>> {{{badmatch,eof},
>>>>> [{couch_file,handle_call,3},
>>>>>  {gen_server,handle_msg,5},
>>>>>  {proc_lib,init_p_do_apply,3}]},
>>>>> {gen_server,call,[<0.82.0>,
>>>>> {pread_bin,86816267188},infinity]}}
>>>>>
>>>>> This is in couch 0.9.0.
>>>>>
>>>>> The file system had run out of disk space previously.  There is
>>>>> sufficient disk space now, but the database file seems to be
>>>>> corrupted.  Is there any utility to try to repair the database?
>>>>>
>>>
>

Mime
View raw message