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: Wed, 1 Jul 2020 13:46:42 -0500 [thread overview]
Message-ID: <9c64b36f-8222-a031-b458-9b15d8e6831f@sandeen.net> (raw)
In-Reply-To: <df054c4d-a1e1-2425-3319-dafa88fc9f08@unibo.it>
On 7/1/20 3:41 AM, Diego Zuccato wrote:
> Il 28/06/20 20:22, Eric Sandeen ha scritto:
>
>> 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.
> Maybe it could be a feature request :)
>
>> I think you'll be limited by the first quota limit that gets reached.
> Verified that. :(
>
> Moreover, I've had troubles at reboot because the superblock did not
> support both group and project quotas. Didn't see anywhere in the docs
> you couldn't have both enabled at the same time. Maybe i'ts just because
> it's an "old" filesystem (IIRC created about 10y ago). I'd suggest a
> "graceful soft failure" in that case: just emit a warning and
> disable/ignore last option requested. Recovery of a remote machine would
> be way easier :)
Hm, yes, worth a look. All 3 have been supported together for quite some
time now, I didn't know it reacted badly on old filesystems.
What did the failure look like?
-Eric
next prev parent reply other threads:[~2020-07-01 18:46 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
2020-07-01 8:41 ` Diego Zuccato
2020-07-01 18:46 ` Eric Sandeen [this message]
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=9c64b36f-8222-a031-b458-9b15d8e6831f@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).