From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] Split default quota limits by quota type
Date: Wed, 27 Jan 2016 11:17:29 -0600 [thread overview]
Message-ID: <56A8FBA9.3060205@sandeen.net> (raw)
In-Reply-To: <20160127153705.GA17571@redhat.com>
On 1/27/16 9:37 AM, Carlos Maiolino wrote:
>>>
>>> This patch aims to split the default quota value by quota type. Allowing each
>>> quota type having different default values.
>>>
>>> Default time limits are still set globally, but I don't mind to split them by
>>> quota type too.
>>
>> Hm, I guess it seems like it should be done; otherwise it's a weird
>> caveat, isn't it? "Default limits are set by type, but timers are
>> inherited from whatever first default quota is found across all types"
>>
>> So yeah, seems like it should be done for timers as well, IMHO;
>> grace periods can be set for each default quota type, so they should
>> be honored.
>>
>
> Ok, I was just working on implement it, but honestly, I don't see the point now
> in split time limits by user/group/project.
>
> grace periods are set globally by default. We don't have specific quota grace
> limits for each user or each group. Just a single value for them.
yeah, sorry about that. I forgot that they were fs-wide, but that makes sense.
Sorry for leading you astray.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-01-27 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 15:18 [PATCH] Split default quota limits by quota type Carlos Maiolino
2016-01-20 17:30 ` Eric Sandeen
2016-01-27 15:37 ` Carlos Maiolino
2016-01-27 17:17 ` Eric Sandeen [this message]
2016-01-27 19:06 ` Eric Sandeen
2016-01-27 22:25 ` Eric Sandeen
2016-01-28 12:35 ` Carlos Maiolino
2016-01-28 14:10 ` 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=56A8FBA9.3060205@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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