I am having an issue with using quota and acl and the same time.
I sent an email to the user list a couple of days ago but didn't hear
anything back.
I am not a programmer, so pardon me if I sounds ignorant. I tried to do
some debugging, and found the following:
In the glusterfs_volfile_reconfigure function, when acl is enabled, the
call to is_graph_topology_equal() returns true.
My debug shows oldvolfile_graph->first and newvolfile_graph->first are
both 0-home. (home is the name of my volume).
However there is a call assignment oldvolfile_graph = ctx->active after
that before calling glusterfs_graph_reconfigure
(oldvolfile_graph, newvolfile_graph).
Based on my debugs, oldvolfile_graph->first now shows
0-posix-acl-autoload, and newvolfile_graph->first shows 0-home.
These are the only differences when running the test with and without
acl. Without acl, oldvolfile_graph->first doesn't get changed to
0-posix-acl-autoload.
Subsequently, I get these messages:
[2012-09-12 13:41:52.297247] I [quota.c:3085:quota_parse_limits]
1-home-quota: no "limit-set" option provided
[2012-09-12 13:41:52.297257] I [quota.c:3097:quota_parse_limits]
1-home-quota: no "timeout" option provided
And I loose all quota function on the client. Can someone help?
Thanks,
...
ling
