From: Carlos Maiolino <cmaiolino@redhat.com>
To: Marco Benatto <mbenatto@redhat.com>
Cc: linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: Re: [PATCH] design: Document project quota inode
Date: Tue, 7 Aug 2018 13:17:21 +0200 [thread overview]
Message-ID: <20180807111721.phuphqqc4mt4uv4h@odin.usersys.redhat.com> (raw)
In-Reply-To: <20180806211032.16777-1-mbenatto@redhat.com>
On Mon, Aug 06, 2018 at 06:10:32PM -0300, Marco Benatto wrote:
> A project quota inode was introduced into V5 superblock allowing
> project quotas and group quotas to be used simultaneously. However
> on "Quota Inodes" section we still mention it's not possible to
> use project and group quotas at sametime.
>
> This patch documents this behavior for V5 and later superblocks,
> while keeps documented the old behavior for earlier versions.
>
> Signed-off-by: Marco Benatto <mbenatto@redhat.com>
> ---
> design/XFS_Filesystem_Structure/internal_inodes.asciidoc | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/design/XFS_Filesystem_Structure/internal_inodes.asciidoc b/design/XFS_Filesystem_Structure/internal_inodes.asciidoc
> index f5c2654..b694e74 100644
> --- a/design/XFS_Filesystem_Structure/internal_inodes.asciidoc
> +++ b/design/XFS_Filesystem_Structure/internal_inodes.asciidoc
> @@ -8,9 +8,12 @@ accessible from the superblock.
> [[Quota_Inodes]]
> == Quota Inodes
>
> -If quotas are used, two inodes are allocated for user and group quota
> -management. If project quotas are used, these replace the group quota management
> -and therefore uses the group quota inode.
> +If quotas are used, prior to version 5 superblocks, two inodes are allocated for
> +user and group management. In this case if project quotas are used, these replace
> +the group quota management and therefore uses the group quota inode.
> +
> +In version 5 superblock or later a third inode will be allocated to project quota
> +management, making it possible to use group and project quotas management simultaneously.
This is mostly ok, but I wonder we the V5 behavior should be emphasized, instead
of V4 behavior?
>
> * Project quota's primary purpose is to track and monitor disk usage for
> directories. For this to occur, the directory inode must have the
> @@ -28,7 +31,7 @@ multiplied by the size of +xfs_dqblk_t+ (136 bytes).
> .Quota inode layout
> image::images/76.png[]
>
> -Quota information is stored in the data extents of the two reserved quota
> +Quota information is stored in the data extents of the reserved quota
> inodes as an array of the +xfs_dqblk+ structures, where there is one array
> element for each ID in the system:
>
> --
> 2.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Carlos
next prev parent reply other threads:[~2018-08-07 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 21:10 [PATCH] design: Document project quota inode Marco Benatto
2018-08-07 11:17 ` Carlos Maiolino [this message]
2018-08-07 13:13 ` Marco Benatto
2018-08-07 15:10 ` Darrick J. Wong
2018-08-07 15:28 ` Darrick J. Wong
2018-08-07 15:30 ` Marco Benatto
2018-08-08 13:12 ` Carlos Maiolino
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=20180807111721.phuphqqc4mt4uv4h@odin.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mbenatto@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;
as well as URLs for NNTP newsgroup(s).