No, it moves the files to a fixed subdirectory (".delete"), and on start-up,
clears out that subdirectory. So if you crash after the rename to the
directory, but before the delete, on the next startup it will complete the
deletion by nuking all the files in that directory.
-Damien
On Jul 28, 2010, at 5:06 PM, Randall Leeds wrote:
> Damien,
> Isn't that the current behavior, too? Now the files are just scattered
> around instead of in one directory.
>
> On Wed, Jul 28, 2010 at 16:28, Damien Katz <[email protected]> wrote:
>> The problem doing it this way is what happens if there is crash between the
>> rename and the actual delete. Then you'l have a large file stuck on the file
>> system, never actually deleted.
>>
>> -Damien
>>
>> On Jul 28, 2010, at 4:20 PM, Robert Newson wrote:
>>
>>> All,
>>>
>>> It used to be possible to mount multiple volumes under
>>> /var/lib/couchdb and direct databases to them using embedded %2f's.
>>> This broke recently when a central .delete directory was introduced.
>>> The file:rename attempts to cross filesystems and fails with EXDEV.
>>>
>>> I have fixed this at
>>> http://github.com/rnewson/couchdb/commit/fbbc42d0787e33ecc894abe50333fc1dcebeb5d5
>>> and would be grateful for a review before I commit to trunk. I think
>>> we want/need this for 1.0.1
>>>
>>> Night,
>>> B.
>>
>>
