[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532648#comment-15532648
]
ASF GitHub Bot commented on AMQ-6441:
-------------------------------------
GitHub user wcrowell opened a pull request:
https://github.com/apache/activemq/pull/202
Fixes AMQ-6441 where a negative value can be returned with large AWS EFS
files systems when calling java.io.File.getTotalSpace()
Fixes AMQ-6441
A test, testLargeFileSystem(), was added to
org.apache.activemq.broker.BrokerServiceTest for checking if the total space on
a volume was too large to fit into a primitive long. If this happens, then
totalSpace is set to java.lang.Long.MAX_VALUE.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wcrowell/activemq master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/202.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #202
----
commit c94b1a2eec78a0fd15763b64dcdff455bfc66e52
Author: William Crowell <[email protected]>
Date: 2016-09-29T12:22:46Z
Fixes AMQ-6441 where a negative value can be returned with large AWS EFS
files systems when calling java.io.File.getTotalSpace()
commit 0c98ecfa2b903ce1301802617b8c5152048364f4
Author: William Crowell <[email protected]>
Date: 2016-09-29T12:24:41Z
Fixes AMQ-6441 where a negative value can be returned with large AWS EFS
files systems when calling java.io.File.getTotalSpace()
----
> Incorrect File System Size Reported with Amazon Elastic File System (EFS)
> -------------------------------------------------------------------------
>
> Key: AMQ-6441
> URL: https://issues.apache.org/jira/browse/AMQ-6441
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.11.1
> Reporter: Ismail Bhana
>
> I've set up Active MQ in production with a shared file system master/slave
> configuration (KahaDB). I've set everything up and mounted the EFS on both
> EC2 instances.
> When I check the disk free stats I get 8 exabytes for the shared file system:
> {code}
> $ df -h
> eu-west-1a.***.efs.eu-west-1.amazonaws.com:/ 8.0E 0 8.0E 0% /mnt/efs
> {code}
> Unfortunately, ActiveMQ cannot interpret this number (8 exabytes). This may
> be due to integer truncation.
> Here is a snippet of the log:
> {code}
> Store limit is 102400 mb (current store usage is 0 mb). The data directory:
> /mnt/efs/kahadb only has -8796093022208 mb of usable space - resetting to
> maximum available disk space: -8796093022207 mb
> Store limit is -8796093022207 mb, whilst the max journal file size for the
> store is: 32 mb, the store will not accept any data when used.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
