From: Carlos Maiolino <cmaiolino@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ilya Pronin <ipronin@twitter.com>, linux-xfs@vger.kernel.org
Subject: Re: Reading/changing projid of a symlink
Date: Fri, 15 Jun 2018 10:57:24 +0200 [thread overview]
Message-ID: <20180615085724.pkpfpmuas5ujmcbw@odin.usersys.redhat.com> (raw)
In-Reply-To: <20180615071236.GA17459@infradead.org>
On Fri, Jun 15, 2018 at 12:12:36AM -0700, Christoph Hellwig wrote:
> On Fri, Jun 15, 2018 at 09:08:29AM +0200, Carlos Maiolino wrote:
> > As I said before, IMHO, I believe the way you are using project quotas is wrong.
> > Project quotas is supposed to be used on a sub-tree based granularity, not on a
> > file based granularity. But again, that's just my opinion.
>
> That is not true. The per-file usage was indeed the original use
> case. The tree quoats implemented using the inheritance were added
> much latter. They are the common use case now, but that doesn't make
> other use cases wrong.
Thanks for the info. I always thought project quotas were designed for
directory-tree granularity, and user/group quotas as a file-based granularity.
But, out of curiosity, if this is not a stupid question...
If project quotas was initially designed as a per-file usage use case in mind,
what would make it different from group quota for example?
> --
> 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-06-15 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 0:26 Reading/changing projid of a symlink Ilya Pronin
2018-06-12 14:36 ` Carlos Maiolino
2018-06-12 22:17 ` Ilya Pronin
2018-06-13 6:23 ` Christoph Hellwig
2018-06-13 14:22 ` Eric Sandeen
2018-06-13 9:40 ` Carlos Maiolino
2018-06-15 0:14 ` Ilya Pronin
2018-06-15 7:08 ` Carlos Maiolino
2018-06-15 7:12 ` Christoph Hellwig
2018-06-15 8:57 ` Carlos Maiolino [this message]
2018-06-15 9:00 ` Christoph Hellwig
2018-06-14 2:31 ` 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=20180615085724.pkpfpmuas5ujmcbw@odin.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=hch@infradead.org \
--cc=ipronin@twitter.com \
--cc=linux-xfs@vger.kernel.org \
/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).