[jira] [Commented] (COUCHDB-1592) Free space check for automatic compaction doesn't follow symlinks

["Robert Newson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492290#comment-13492290 ] 

Robert Newson commented on COUCHDB-1592:
----------------------------------------

Can you tell me if filename:absname("path to your symlink") returns the resolved path to your symlink? Also, the output of disksup:get_disk_data() would be useful. I've found that disksup:get_disk_data() is not perfect (it gets confused by volumes with spaces in the name, etc).

I have alternate code to find the right match in disksup's messy output from my own compaction daemon, I'd be interested to know if it finds the right result;

capacity(RootDir) ->
DiskData = lists:sort(fun({A,_,_}, {B,_,_}) -> length(A) >= length(B) end, disksup:get_disk_data()),
[Capacity|_] = [C || {Id, K, C} <- DiskData, lists:prefix(Id, RootDir)],
Capacity.

A call of capacity("/mnt/somewhere") should return a number reflecting the percentage of disk space used.

                
> 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