[Bugs] [Bug 1115197] Directory quota does not apply on it's sub-directories

bugzilla at redhat.com bugzilla at redhat.com
Mon Feb 23 12:56:56 UTC 2015


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



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9510 committed in release-3.5 by Niels de Vos
(ndevos at redhat.com) 
------
commit 6518a79634ba505ed06e930907ebf956f8784b7d
Author: vmallika <vmallika at redhat.com>
Date:   Fri Jan 30 12:10:38 2015 +0530

    features/quota: Send the immediate parent with limit in quota statfs
    adjustment

    This is a backport of http://review.gluster.org/#/c/7330

    > Problem:
    > Assume the directory structure /quota_limit_dir/subdir and
    > quota_limit_dir is
    > set with some limit. When quota-deem-statfs is enabled the output of
    > 'df /quota_limit_dir' would display quota modified values wrt to
    > quota_limit_dir where as 'df /quota_limit_subdir/subdir' would display
    > the quota modified values wrt volume root (/).
    >
    > This behaviour is not expected since, when mounted with subdirectory
    > admin doesn't want users to know information above the subdirectory
mounted.
    >
    > Solution:
    > Any subdirectory within a quota_limit_dir would show the modified values
    > as in the /quota_limit_dir. It searches for the nearest parent that has
quota
    > limit set and modifies the statvfs wrt that.
    >
    > Change-Id: Ie10fae8999bddbb766b1dbeb881723ed80dce688
    > BUG: 1080296
    > Signed-off-by: Varun Shastry <vshastry at redhat.com>
    > Reviewed-on: http://review.gluster.org/7330
    > Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    > Tested-by: Raghavendra G <rgowdapp at redhat.com>

    Change-Id: I5232a82da20d3dfd48303ba2748b86cfc96ff864
    BUG: 1115197
    Signed-off-by: vmallika <vmallika at redhat.com>
    Reviewed-on: http://review.gluster.org/9510
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>

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


More information about the Bugs mailing list