[
https://issues.apache.org/jira/browse/COUCHDB-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492340#comment-13492340
]
Nils Breunese commented on COUCHDB-1592:
----------------------------------------
I don't think our admins would ever change the target of that symlink while
applications are running. Could CouchDB cope with something like that? Either
way I still don't really see what the problem would be. Free disk space needs
to be determined. If the target of the symlink changes the free disk space
changes, but as far as I can see this is no problem since free disk space is
evaluated when compaction is started. What do you think could go wrong?
> Free space check for automatic compaction doesn't follow symlinks
> -----------------------------------------------------------------
>
> Key: COUCHDB-1592
> URL: https://issues.apache.org/jira/browse/COUCHDB-1592
> 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: http://www.atlassian.com/software/jira
