From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 20:42:33 -0400 [thread overview]
Message-ID: <8c0e17fb-41e3-753c-9678-04e410825dce@kilonet.net> (raw)
In-Reply-To: <CMM.0.95.0.1559262062.beebe@gamma.math.utah.edu>
On 5/30/2019 8:21 PM, Nelson H. F. Beebe wrote:
> Several list members report having used, or suffered under, filesystem
> quotas.
>
> At the University Utah, in the College of Science, and later, the
> Department of Mathematics, we have always had an opposing view:
>
> Disk quotas are magic meaningless numbers imposed by some bozo
> ignorant system administrator in order to prevent users from
> getting their work done.
You've never had people like me on your systems ;) - But yeah...
> For the last 15+ years, our central fileservers have run ZFS on
> Solaris 10 (SPARC, then on Intel x86_64), and for the last 17 months,
> on GNU/Linux CentOS 7.
>
I do the same with ZFS - limit the individual filesystems with "zfs set
quota=xxx" so the entire pool can't be filled. I assign a zfs filesystem
to an individual user in /export/home and when they need more, they let
me know. Various monitoring scripts tell me when a filesystem is
approaching 80%, and I either just expand it on my own because of the
user's usage, or let them know they are approaching the limit.
Same thing with Netbackup Basic Disk pools in a common ZFS pool. I can
adjust them as needed, and Netbackup sees the change almost immediately.
At home, I did this with my kids ;) - Samba and zfs quota on the
filesystem let them know how much room they had.
art k.
PS: I'm starting to move to FreeBSD and ZFS for VMware datastores, the
performance is outstanding over iSCSI on 10Gbe - (which Solaris 11's
COMSTAR is not apparently very good at especially with small block
sizes). I have yet to play with Linux and ZFS but would appreciate to
hear (privately, if it's not appropriate for the list) your experiences
with it.
next prev parent reply other threads:[~2019-05-31 0:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 0:21 Nelson H. F. Beebe
2019-05-31 0:37 ` Larry McVoy
2019-05-31 0:42 ` Arthur Krewat [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2019-05-30 16:04 Noel Chiappa
2019-05-30 16:48 ` KatolaZ
2019-05-30 17:42 ` ron
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
2019-06-01 0:30 ` reed
2019-06-04 13:50 ` Tony Finch
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=8c0e17fb-41e3-753c-9678-04e410825dce@kilonet.net \
--to=krewat@kilonet.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).