[Bugs] [Bug 1172348] new installation of glusterfs3.5.3-1; quota not displayed to client.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1172348



--- Comment #5 from Khoi Mai <khoi.mai2008 at gmail.com> ---
It appears that my upgrade from glusterfs-3.4.3 to glusterfs-3.5.3. All my
'quota limits' have been reset on all my volumes.

The reason I'm saying that is because the quota limits that I did have; I
listed them after all the storage nodes (4 in total) they replied back with "no
quota limit for this volume"

I had 12 volumes I had to recreate the quota limit-usage for again.

After recreating the limits their was a localhost mount for all my volumes:

localhost:dyn_job     5.0G   11M  5.0G   1% /var/run/gluster/dyn_job
localhost:dyn_avr     5.0G     0  5.0G   0% /var/run/gluster/dyn_avr
localhost:dyn_ctl     5.0G  1.5G  3.6G  29% /var/run/gluster/dyn_ctl
localhost:dyn_ert      10G  5.0G  5.1G  50% /var/run/gluster/dyn_ert
localhost:dyn_wls     5.0G  2.7G  2.4G  53% /var/run/gluster/dyn_wls
localhost:dyn_mech    5.0G   69M  5.0G   2% /var/run/gluster/dyn_mech
localhost:dyn_admin   5.0G  672M  4.4G  14% /var/run/gluster/dyn_admin
localhost:dyn_cfu     5.0G  3.0G  2.1G  60% /var/run/gluster/dyn_cfu
localhost:devstatic   1.5T  818G  719G  54% /var/run/gluster/devstatic
localhost:dyn_eng     5.0G  896K  5.0G   1% /var/run/gluster/dyn_eng

I know if I recycle glusterd, nothing changes.  If i kill all gluster process,
the mounts will error with "end transport not connected".

So I decided to reboot this server that was the only one that had the local
mounts and after reboot they were all gone.

I would expect in an upgrade my quota limits would be preserved.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.