Red Hat Bugzilla – Bug 848244
[6d19136de7af9135dd23662f18c3ee544a2888da]: df does not show quota limit for clients which are mounted before enabling quota
Last modified: 2014-08-11 19:22:27 EDT
+++ This bug was initially created as a clone of Bug #795735 +++
Description of problem:
root@Dagobah:/data/mounts/mount# df -h
dagobah:vol 84G 807M 83G 1% /data/mounts/mount
dagobah:vol 5.0G 0 5.0G 0% /data/mounts/nfs
dagobah:vol 5.0G 30M 5.0G 1% /data/mounts/fuse
root@Dagobah:/data/mounts/mount# gluster volume info
Volume Name: vol
Volume ID: ae583de9-8fef-4c6e-b66f-450dfb587f39
Number of Bricks: 2 x 2 = 4
/data/mounts/mount was mounted before quota limit was set, & after setting the limit , df does not show updated limit.
df (ie, statvfs()) call is for the mounted filesystem, while quota is for a volume, which would have directory quota enabled, thus, its not fair to make df behave differently depending on the quota value.
df should always not bother about quota, and quota limits should be fetched by different quota command (in our case 'gluster quota limit-usage ').