You can find the fix at: http://review.gluster.com/#change,3949 ----- Original Message ----- > From: "Raghavendra Gowdappa" <rgowdapp at redhat.com> > To: "Ling Ho" <ling at slac.stanford.edu> > Cc: Gluster-users at gluster.org, "Vijay Bellur" <vbellur at redhat.com>, "Amar Tumballi" <atumball at redhat.com> > Sent: Monday, September 17, 2012 4:12:53 PM > Subject: Re: 3.3 Quota Problems > > Hi Ling, > > A bug has been filed at > https://bugzilla.redhat.com/show_bug.cgi?id=857874 > > Thanks for reporting. > > regards, > Raghavendra. > ----- Original Message ----- > > From: "Ling Ho" <ling at slac.stanford.edu> > > To: Gluster-users at gluster.org > > Sent: Wednesday, September 12, 2012 1:34:34 AM > > Subject: Re: 3.3 Quota Problems > > > > I found this only happens when I mount the volume with the "acl" > > option. > > Otherwise, I don't get the "no limit-set option provided" message, > > and > > things works fine. Not even needing the remount the volume to see > > changes to quota. > > > > ... > > ling > > > > On 09/10/2012 07:15 PM, Ling Ho wrote: > > > I found these in the client log: > > > > > > [2012-09-10 18:56:07.728206] I > > > [glusterfsd-mgmt.c:64:mgmt_cbk_spec] > > > 0-mgmt: Volume file changed > > > [2012-09-10 18:56:08.751162] D > > > [glusterfsd-mgmt.c:1441:is_graph_topology_equal] > > > 0-glusterfsd-mgmt: > > > graphs are equal > > > [2012-09-10 18:56:08.751175] D > > > [glusterfsd-mgmt.c:1495:glusterfs_volfile_reconfigure] > > > 0-glusterfsd-mgmt: Only options have changed in the new graph > > > [2012-09-10 18:56:08.751192] D > > > [options.c:925:xlator_reconfigure_rec] > > > 0-ana03-dht: reconfigured > > > [2012-09-10 18:56:08.751200] I [quota.c:3085:quota_parse_limits] > > > 0-ana03-quota: no "limit-set" option provided > > > ... > > > ling > > > > > > > > > > > > On 09/10/2012 03:01 PM, Ling Ho wrote: > > >> I am trying to use directory quota in our environment and face > > >> two > > >> problems: > > >> > > >> 1. When new quota is set on a directory, it doesn't take effect > > >> until > > >> the volume is remounted on the client. This is a major > > >> inconvenience. > > >> > > >> 2. If I add a new quota, quota stops working on the client. > > >> > > >> This is how to reproduce problem #2. > > >> > > >> I have these directories under my volume ana03: > > >> > > >> ling > > >> ling/testdir > > >> > > >> # gluster volume quota ana03 limit-usage /ling 20GB > > >> > > >> I could write into the directory "ling" till it is over 20GB and > > >> it > > >> gives me a Disk quota exceeded error. > > >> > > >> However, if I then set quota for "ling/testdir", without > > >> remonting > > >> the > > >> volume on the client > > >> > > >> # gluster volume quota ana03 limit-usage /ling/testdir 2GB > > >> > > >> Not only I can write more than 2GB under "ling/testdir", I could > > >> now > > >> write more than 20GB under "ling". > > >> > > >> Remounting the volume on the client fixes everything. > > >> > > >> I am using glusterfs-3.3.0-1 on both the client and server. The > > >> server > > >> is running RHEL6.3, and client running RHEL5.8. > > >> > > >> Any idea about these problem, and if there is a fix? > > >> > > >> Thanks. > > >> ... > > >> ling > > >> > > >> > > >> _______________________________________________ > > >> Gluster-users mailing list > > >> Gluster-users at gluster.org > > >> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > > > _______________________________________________ > > Gluster-users mailing list > > Gluster-users at gluster.org > > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > >
