On Thu, Dec 03, 2020 at 02:00:42PM -0600, Eric Sandeen wrote:
> Ever since
> 89605011915a ("xfs: include reservations in quota reporting")
> xfs quota has been in sync with delayed allocations, so this caveat
> is no longer relevant or correct; remove it.
>
> Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx>
Looks good,
Reviewed-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>
--D
> ---
> man/man8/xfs_quota.8 | 11 +----------
> 1 file changed, 1 insertion(+), 10 deletions(-)
>
> diff --git a/man/man8/xfs_quota.8 b/man/man8/xfs_quota.8
> index b3c4108e..bfdc2e4f 100644
> --- a/man/man8/xfs_quota.8
> +++ b/man/man8/xfs_quota.8
> @@ -725,17 +725,8 @@ Same as above without a need for configuration files.
> .in -5
> .fi
> .SH CAVEATS
> -XFS implements delayed allocation (aka. allocate-on-flush) and this
> -has implications for the quota subsystem.
> -Since quota accounting can only be done when blocks are actually
> -allocated, it is possible to issue (buffered) writes into a file
> -and not see the usage immediately updated.
> -Only when the data is actually written out, either via one of the
> -kernels flushing mechanisms, or via a manual
> -.BR sync (2),
> -will the usage reported reflect what has actually been written.
> .PP
> -In addition, the XFS allocation mechanism will always reserve the
> +The XFS allocation mechanism will always reserve the
> maximum amount of space required before proceeding with an allocation.
> If insufficient space for this reservation is available, due to the
> block quota limit being reached for example, this may result in the
> --
> 2.17.0
>
>
