Hi Abhi,
On 12/02/15 16:54, Abhi Das wrote:
This patch allows gfs2_quota_check() to take an extra argument
called 'exp_change'. Prior to any allocation, gfs2_quota_check()
or gfs2_quota_lock_check() is called with exp_change containing
the number of blocks we expect to allocate in this
- Original Message -
- Original Message -
Hi Bob,
On 22/01/15 20:41, Bob Peterson wrote:
Hi,
This patch changes the old block_map structure for fsck.gfs2 to the
simpler bitmap structure so that we have a 1:1 correspondence. This
was done to reduce memory
- Original Message -
From: Andrew Price anpr...@redhat.com
To: Abhi Das a...@redhat.com, cluster-devel@redhat.com
Sent: Thursday, February 12, 2015 12:12:50 PM
Subject: Re: [Cluster-devel] [GFS2 PATCH 1/4] gfs2: check quota for blocks
we're about to allocate
Hi Abhi,
On
When removing a default acl or setting an access acl that is entirely
represented in the file mode, we end up with acl == NULL in gfs2_set_acl(). In
that case, bring gfs2 in line with other file systems and cache the NULL acl
with set_cached_acl() instead of invalidating the cache with
This is a variant of the existing gfs2_inplace_reserve() function.
If the requested number of blocks are not available to be reserved
from any of the rgrps, gfs2_inplace_reserve() return -ENOSPC.
gfs2_inpl_rsrv_ret_max_val() will also return the maximum blocks
available in an extra parameter
These patches are related to bz1174295 where fallocate could
exceed quota. I'm posting these for early feedback as these
patches are only compile-tested so far.
patch 1 - This is the patch that actually addresses the quota
exceed issue. Quota checks were not being performed
With the addition of gfs2_quota_lck_chk_ret_allow() and
gfs2_inpl_rsrv_ret_max_avl(), we can quickly get an estimate of
how many more blocks are available for allocation restricted by
quota and fs size respectively.
By trying to allocate what's available instead of guessing, we
can max out quotas
This patch allows gfs2_quota_check() to take an extra argument
called 'exp_change'. Prior to any allocation, gfs2_quota_check()
or gfs2_quota_lock_check() is called with exp_change containing
the number of blocks we expect to allocate in this operation.
gfs2_quota_check() will add this number to
gfs2_quota_chk_ret_allow and gfs2_quota_lck_chk_ret_allow are
variants of gfs2_quota_check and gfs2_quota_lock_check respectively.
If an operation will not succeed due to a quota violation, these
functions will return the number of blocks that quota will actually
allow without failing in an extra
- Original Message -
These patches are related to bz1174295 where fallocate could
exceed quota. I'm posting these for early feedback as these
patches are only compile-tested so far.
patch 1 - This is the patch that actually addresses the quota
exceed issue. Quota checks were
10 matches
Mail list logo
