couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nils Breunese (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1592) Free space check for automatic compaction doesn't seem to follow symlinks
Date Wed, 07 Nov 2012 11:51:12 GMT


Nils Breunese commented on COUCHDB-1592:

> It sounds like couchdb is doing exactly what you told it, to me.

I guess that's how you look at it. CouchDB thinks it can only write 1 GB of data to the data
directory, but that is not true. So in my opinion this is a bug as CouchDB should be looking
at how much data it can really write to the configured location.

> Why can't you tell couchdb where your data is really stored?

First of all it's not my call as I'm not administering the systems our production CouchDB
is running on, but I believe our hoster is using symlinks for flexibility of moving around
storage. They want to be able to move the data to another storage system and not have to update
all configuration files for all applications on their platform.
> Free space check for automatic compaction doesn't seem to follow symlinks
> -------------------------------------------------------------------------
>                 Key: COUCHDB-1592
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Nils Breunese
> We've got a problem with automatic compaction not running due to low diskspace according
to CouchDB. According to our system administrators there is more than enough space (more than
twice the currently used space), but the data directory is a symlink to the real data storage.
It seems CouchDB is checking the diskspace on the filesystem on which the symlink resides
instead of the diskspace on the linked filesystem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message