[AMQ-6441] Incorrect File System Size Reported with Amazon Elastic File System (EFS)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.11.1
• Fix Version/s: 5.15.0
• Assignee: Gary Tully
• Reporter: Ismail Bhana
• Created: 23/Sep/16 14:26
• Updated: 27/Jan/18 20:32
• Resolved: 08/Dec/16 11:18

Description

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:

$ df -h 
eu-west-1a.***.efs.eu-west-1.amazonaws.com:/  8.0E     0  8.0E   0% /mnt/efs 

Unfortunately, ActiveMQ cannot interpret this number (8 exabytes). This may be due to integer truncation.

Here is a snippet of the log:

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. 

Issue Links

• is related to: ARTEMIS-872 On extremely large volumes, Artemis falsely reports "Storage usage is beyond max-disk-usage"
• is related to: CASSANDRA-13067 Integer overflows with file system size reported by Amazon Elastic File System (EFS)
• links to: GitHub Pull Request #202