From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Fri, 31 May 2019 14:43:01 -0600 [thread overview]
Message-ID: <8d220e00-c908-5e3c-48d1-927790385ca0@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <78485efd-2cd3-a290-8142-48672bb847c5@nomadlogic.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
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?
> I was briefly on the team responsible for managing these quotas for a
> show and it was seriously an around the clock operation to keep our disks
> from filling up. One of the tricks was to figure out how much space a
> rendered sequence of images would consume, factor in the time-to-render
> a frame and attempt to line up your backup jobs to free up enough space
> so the render nodes could write out the images to NFS.
Intriguing.
Thank you for sharing.
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4008 bytes --]
next prev parent reply other threads:[~2019-05-31 20:43 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 [this message]
2019-05-31 20:59 ` Pete Wright
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=8d220e00-c908-5e3c-48d1-927790385ca0@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).