public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] xfs_quota: Remove delalloc caveat from man page
Date: Thu, 3 Dec 2020 12:08:05 -0800	[thread overview]
Message-ID: <20201203200805.GK106272@magnolia> (raw)
In-Reply-To: <8fe85780-d68e-6d33-349b-66dad73858c3@redhat.com>

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@redhat.com>

Looks good,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--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
> 
> 

  reply	other threads:[~2020-12-03 20:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 19:53 [PATCH 0/3] xfs_quota: man page fixups Eric Sandeen
2020-12-03 20:00 ` [PATCH 1/3] xfs_quota: document how the default quota is stored Eric Sandeen
2020-12-03 20:07   ` Darrick J. Wong
2020-12-03 20:12     ` Eric Sandeen
2020-12-03 20:38       ` Darrick J. Wong
2020-12-03 20:36   ` [PATCH 1/3 V2] " Eric Sandeen
2020-12-03 20:46   ` [PATCH 1/3 V3] " Eric Sandeen
2020-12-03 21:20     ` Darrick J. Wong
2020-12-03 20:00 ` [PATCH 2/3] xfs_quota: Remove delalloc caveat from man page Eric Sandeen
2020-12-03 20:08   ` Darrick J. Wong [this message]
2020-12-03 20:01 ` [PATCH 3/3] xfs_quota: make manpage non-male-specific Eric Sandeen
2020-12-03 20:10   ` Darrick J. Wong
2020-12-03 20:15     ` Eric Sandeen
2020-12-03 20:33   ` [PATCH 3/3 V2] xfsprogs: make things non-gender-specific Eric Sandeen
2020-12-03 20:40     ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201203200805.GK106272@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox