From: Eric Sandeen <sandeen@sandeen.net>
To: Diego Zuccato <diego.zuccato@unibo.it>, linux-xfs@vger.kernel.org
Subject: Re: Separate user- and project- quota ?
Date: Sun, 28 Jun 2020 13:22:05 -0500 [thread overview]
Message-ID: <2c0bfee3-01cc-65cf-2be1-1af9432a18be@sandeen.net> (raw)
In-Reply-To: <93882c1f-f26e-96c7-0a60-68fc9381e36c@unibo.it>
On 6/26/20 5:58 AM, Diego Zuccato wrote:
> Hello all.
>
> I'd need to have separate quota for users and projects on the same
> filesystem.
> I currently have /home/PERSONALE and /home/STUDENTI where homes gets
> automatically created. I'd need to have /home/software/prjN directories
> with independent quotas.
>
> What I've seen is that if any user creates a file in prjN directory,
> that file is counted twice: both in user's and project's quota.
>
> Am I getting something wrong? Missing an option? Can it be done?
>
> TIA.
I'm not certain, but I don't think there is any sort of hierarchy or
priority among the 3 quota types on a given filesystem.
In the same way that if you have user & group quotas active, a file
in a user:group pair would count against user and group limits, I'm
fairly certain that the same behavior applies to user & project quotas.
I think what you're asking is whether a file in a project quota directory
can avoid user quota accounting, and I'm pretty sure the answer is no.
I think you'll be limited by the first quota limit that gets reached.
The way around this would be to make /home/software/ a separate filesystem
with only project quotas active.
(Apologies for not digging into the code to be certain, but from what
you've seen and from what I think I know, the above is my best guess.)
-Eric
next prev parent reply other threads:[~2020-06-28 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 10:58 Separate user- and project- quota ? Diego Zuccato
2020-06-28 18:22 ` Eric Sandeen [this message]
2020-07-01 8:41 ` Diego Zuccato
2020-07-01 18:46 ` Eric Sandeen
2020-07-02 6:14 ` Diego Zuccato
2020-07-02 11:34 ` Brian Foster
2020-07-02 12:15 ` Diego Zuccato
2020-07-02 12:50 ` Brian Foster
2020-07-04 15:21 ` Eric Sandeen
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=2c0bfee3-01cc-65cf-2be1-1af9432a18be@sandeen.net \
--to=sandeen@sandeen.net \
--cc=diego.zuccato@unibo.it \
--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).