Should have included that fact that there are many of these entries in the logs
with quotas enabled:
"... quota context not set in inode ..."
google tells me this should be fixed soon
(http://thr3ads.net/gluster-users/2013/08/2670145-Quota-context-not-set-in-inode),
I wonder if this is related to my original query below.
On Dec 10, 2013, at 2:04 PM, sudowrestler wrote:
> Using gluster 3.4, I set up a replicated, distributed volume using a
private network. Remote clients use NFS over the public network to connect. With
quotas enabled, a user cannot mv a file, gets an "Error occurred on the
server or IO Error" message, and the gluster nfs log says "...
rename...failed...Cannot allocate memory." With quotas disabled, everything
works fine.
>
> Ideas?
>
> Jim