From: Pete Wright <pete@nomadlogic.org>
To: Grant Taylor <gtaylor@tnetconsulting.net>, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Fri, 31 May 2019 13:59:58 -0700 [thread overview]
Message-ID: <37bb9b7a-518d-9d7f-5c63-ee12346885d2@nomadlogic.org> (raw)
In-Reply-To: <8d220e00-c908-5e3c-48d1-927790385ca0@spamtrap.tnetconsulting.net>
On 5/31/19 1:43 PM, Grant Taylor via TUHS wrote:
> On 5/31/19 1:07 PM, Pete Wright wrote:
>> An individual user was given something like 1GB by default (here they
>> had their mailbox, source-code, scripts etc), then the show they were
>> booked on was then given an allocation of say 1TB of storage.
>
> It sounds like you are talking about group quotas in addition to each
> individual user's /user/ quota. Is that correct? Or was this more an
> imposed file system limit in lieu of group quotas?
it was a mix, $HOME was tied to a specific UID.
for show data we leveraged per-volume quotas. our directory structure
was setup in such a way that a a path would be a series of symlinks
pointing for specific NFS volumes. so /shot/sequence/render for example
could reference multiple volumes. /shot/sequence would live on a
separate filer than "render". we could also move around where "render"
would live and not have to worry about creating orphan paths and such.
this was a common practice to manage hotspots, or for maint windows etc.
the net result was we used a mix of volume quotas that netapp managed in
addition to higher level shot/show quotas which were calculated out of
band by some in-house services.
-pete
--
Pete Wright
pete@nomadlogic.org
@nomadlogicLA
next prev parent reply other threads:[~2019-05-31 21:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 13:49 David
2019-05-30 14:23 ` Diomidis Spinellis
2019-05-30 14:26 ` Dan Cross
2019-05-30 14:27 ` Rico Pajarola
2019-05-31 7:16 ` George Ross
2019-05-30 14:29 ` Robert Brockway
2019-05-30 14:34 ` Theodore Ts'o
2019-05-30 14:48 ` John P. Linderman
2019-05-30 14:57 ` Jim Geist
2019-05-30 14:55 ` Andreas Kusalananda Kähäri
2019-05-30 15:00 ` KatolaZ
2019-05-30 17:28 ` Grant Taylor via TUHS
2019-05-30 19:19 ` Michael Kjörling
2019-05-30 20:42 ` Warner Losh
2019-05-30 22:23 ` George Michaelson
2019-05-31 1:36 ` alan
2019-05-31 19:07 ` Pete Wright
2019-05-31 20:43 ` Grant Taylor via TUHS
2019-05-31 20:59 ` Pete Wright [this message]
2019-06-01 0:30 ` reed
2019-06-04 13:50 ` Tony Finch
2019-05-30 16:04 Noel Chiappa
2019-05-30 16:48 ` KatolaZ
2019-05-30 17:42 ` ron
2019-05-31 0:21 Nelson H. F. Beebe
2019-05-31 0:37 ` Larry McVoy
2019-05-31 0:42 ` Arthur Krewat
2019-05-31 15:05 ` Nelson H. F. Beebe
2019-05-31 16:06 ` Michael Kjörling
2019-05-31 16:15 ` Grant Taylor via TUHS
2019-05-31 16:38 ` Michael Kjörling
2019-05-31 15:55 ` Rico Pajarola
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=37bb9b7a-518d-9d7f-5c63-ee12346885d2@nomadlogic.org \
--to=pete@nomadlogic.org \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.tuhs.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).