From: Dave Chinner <david@fromorbit.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Wang Shilong <wangshilong1991@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net, lixi@ddn.com,
Andreas Dilger <adilger@dilger.ca>,
Wang Shilong <wshilong@ddn.com>,
linux-man <linux-man@vger.kernel.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH 2/2] statx.2: add project support update
Date: Tue, 5 Mar 2019 07:50:06 +1100 [thread overview]
Message-ID: <20190304205006.GX23020@dastard> (raw)
In-Reply-To: <CAKgNAkitiDEYSZDnJ5iQ6coaE=q45BHxnG2z_bZtWs=kk+2g3w@mail.gmail.com>
On Mon, Mar 04, 2019 at 02:52:59PM +0100, Michael Kerrisk (man-pages) wrote:
> Hello Wang Shilong,
>
> On Fri, 1 Mar 2019 at 15:06, Wang Shilong <wangshilong1991@gmail.com> wrote:
> >
> > From: Wang Shilong <wshilong@ddn.com>
>
> I take it that these patches relate to some API changes that are not
> yet merged into the kernel, right?
>
> Also, I think we need some accompanying info to describe project IDs.
> Can you point me at any documents/resources?
Probably "best" documented in the man pages that ship with xfsprogs.
Basically, it's just another quota ID that can be used to account
for files/directories in arbitrary admin defined groups. i.e. quotas
that aren't bound by user/group identities.
$ man 8 xfs_quota
$ man 5 projects
$ man 5 projid
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-03-04 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 14:06 [PATCH 1/2] fchownat.2: add project support updates Wang Shilong
2019-03-01 14:06 ` [PATCH] statx: test statx support for project Wang Shilong
2019-03-01 14:06 ` [PATCH 2/2] statx.2: add project support update Wang Shilong
2019-03-01 15:51 ` Darrick J. Wong
2019-03-04 13:52 ` Michael Kerrisk (man-pages)
2019-03-04 20:50 ` Dave Chinner [this message]
2019-03-04 21:16 ` Michael Kerrisk (man-pages)
2019-03-04 23:17 ` Dave Chinner
2019-03-04 22:56 ` Eugene Syromyatnikov
2019-03-03 23:08 ` [PATCH 1/2] fchownat.2: add project support updates Dave Chinner
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=20190304205006.GX23020@dastard \
--to=david@fromorbit.com \
--cc=adilger@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lixi@ddn.com \
--cc=mtk.manpages@gmail.com \
--cc=wangshilong1991@gmail.com \
--cc=wshilong@ddn.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).