Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Date: Fri, 2 Sep 2016 08:30:40 -0700 (PDT)
From: ishmeister <ibhana@visibilityltd.com>
To: users@activemq.apache.org
Message-ID: <1472830240388-4716113.post@n4.nabble.com>
In-Reply-To: <CAPVVMa-9vSvLeWBmz3LAVxs5kSHcao3s_sU4ZqYe25uiF2vkhA@mail.gmail.com>
References: <1472113019331-4715818.post@n4.nabble.com> <CABVfffLwx3O=EBXskgC-fUO_D1yUrDVQrR6yORxQZX9G=JerOA@mail.gmail.com> <CAPVVMa-9vSvLeWBmz3LAVxs5kSHcao3s_sU4ZqYe25uiF2vkhA@mail.gmail.com>
Subject: Re: Active MQ Shared File System Master Slave with Elastic File
 System
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Sep 2016 15:33:18 -0000

Tim,

I contacted AWS tech support and their response was this:

"I've checked with our EFS team to see if there is any EFS-related
workaround they can offer. Unfortunately, they have confirmed that this is
EFS intended behavior and there is no way of mounting a filesystem with
"predetermined size" or change the way it is reported by the OS that they or
myself know of."

The OS in my case was Ubuntu 14.04. 

Korny, thanks for the tips.


--
View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-Shared-File-System-Master-Slave-with-Elastic-File-System-tp4715818p4716113.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.