From: Mike Fedyk <mfedyk@matchmail.com>
To: James Sutherland <jas88@cam.ac.uk>,
Ben Greear <greearb@candelatech.com>,
Neil Brown <neilb@cse.unsw.edu.au>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RFC - tree quotas for Linux (2.4.12, ext2)
Date: Thu, 18 Oct 2001 15:56:36 -0700 [thread overview]
Message-ID: <20011018155636.B2467@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3BCE6E6E.3DD3C2D6@candelatech.com> <Pine.SOL.4.33.0110180937420.13081-100000@yellow.csi.cam.ac.uk> <20011018132035.A444@mikef-linux.matchmail.com> <20011018151718.O1144@turbolinux.com>
In-Reply-To: <20011018151718.O1144@turbolinux.com>
On Thu, Oct 18, 2001 at 03:17:18PM -0600, Andreas Dilger wrote:
> On Oct 18, 2001 13:20 -0700, Mike Fedyk wrote:
> > Actually, it looks like Niel is creating a two level Quota system. In ther
> > normal quota system, if you own a file anywhere, it is attributed to you.
> > But, in the tree quota system, it is attributed to the owner of the tree...
>
> Hmm, we already have group quotas, and (excluding ACLs) you would need to
> have group write permission into the tree to be able to write there. How
> does the tree quota help us in the end? Either users are "nice" and you
> don't need quotas, or users are "not nice" and you don't want them to be
> able to dump their files into an area that doesn't keep them "in check" as
> quotas are designed to do.
>
Hmm, I think I just thought of a use for the tree quota concept.
Lets say that you have about 50GB of space, but you only want to allow 20GB
for a certain tree (possibly mp3s), and you want to keep user ownerships of
the files they contribute.
Now try to use the group quota idea.
User makes mp3
user can chgrp to any user that they are a member of...
copy to /mp3s.
Now the group (and quota) that was setup for mp3s has been circumvented.
With the tree quota, an entire tree could be assigned to a certain group,
and then use the group quota tools...
The only other way I can see to fix this would be a cron job to walk the
tree and set the group to whatever has been setup, but that looks like a
hack to me.
Is there another way to fix this besides putting all mp3s on a separate
partition?
Mike
next prev parent reply other threads:[~2001-10-18 22:56 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 5:06 RFC - tree quotas for Linux (2.4.12, ext2) Neil Brown
2001-10-18 5:53 ` Ben Greear
2001-10-18 8:38 ` James Sutherland
2001-10-18 20:20 ` Mike Fedyk
2001-10-18 20:47 ` Tim Walberg
2001-10-19 1:07 ` Neil Brown
2001-10-19 3:03 ` Rik van Riel
2001-10-19 11:50 ` Horst von Brand
2001-10-19 17:00 ` Mike Fedyk
2001-10-18 21:17 ` Andreas Dilger
2001-10-18 22:56 ` Mike Fedyk [this message]
2001-10-19 0:14 ` Horst von Brand
2001-10-19 0:51 ` Mike Fedyk
2001-10-19 1:13 ` Neil Brown
2001-10-19 0:53 ` Neil Brown
2001-10-24 15:16 ` Jan Kara
2001-10-24 15:34 ` James Sutherland
2001-10-24 15:39 ` Jan Kara
2001-10-24 15:50 ` James Sutherland
2001-10-24 17:41 ` Rik van Riel
2001-10-24 18:08 ` James Sutherland
2001-10-26 11:25 ` Pavel Machek
2001-10-24 21:24 ` Neil Brown
2001-10-25 15:48 ` Jan Kara
2001-10-26 4:36 ` Neil Brown
2001-10-29 14:06 ` Jan Kara
2001-10-29 23:23 ` Neil Brown
2001-10-30 12:33 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 3:00 Toivo Pedaste
2001-10-19 4:39 ` Neil Brown
2001-10-24 18:44 Jesse Pollard
2001-10-25 6:15 ` Albert D. Cahalan
[not found] <fa.inl6g6v.1mmbp4@ifi.uio.no>
[not found] ` <fa.heevhav.sjs8an@ifi.uio.no>
2001-11-18 22:15 ` Swap Dan Maas
2001-11-18 22:43 ` Swap François Cami
2001-11-19 9:18 ` Swap James A Sutherland
2001-11-19 10:51 ` Swap Remco Post
2001-11-19 13:33 ` Swap James A Sutherland
2001-11-19 13:46 ` Swap Remco Post
2001-11-19 16:58 ` Swap Rik van Riel
[not found] ` <Pine.LNX.4.33L.0111191458150.1491-100000@duckman.distro.conecti va>
2001-11-19 21:13 ` Swap Alex Bligh - linux-kernel
2001-11-19 21:17 ` Swap Rik van Riel
[not found] ` <Pine.LNX.4.33L.0111191917000.1491-100000@duckman.distro.conecti va>
2001-11-19 21:52 ` Swap Alex Bligh - linux-kernel
2001-11-19 16:36 ` Swap Jesse Pollard
2001-11-20 14:51 ` Swap J.A. Magallon
2001-11-20 16:01 ` Swap Wolfgang Rohdewald
2001-11-20 16:06 ` Swap Remco Post
2001-11-20 16:12 ` Swap Nick LeRoy
2001-11-20 16:20 ` Swap Richard B. Johnson
2001-11-20 17:14 ` Swap Christopher Friesen
2001-11-20 17:40 ` Swap Richard B. Johnson
2001-11-20 18:14 ` Swap Nick LeRoy
2001-11-21 10:17 ` Swap Helge Hafting
2001-11-21 11:17 ` Swap Alan Cox
2001-11-20 23:20 ` Swap Luigi Genoni
2001-11-21 16:44 ` Swap Remco Post
2001-11-20 17:58 ` Swap Wolfgang Rohdewald
2001-11-26 21:51 ` [Linux-abi-devel] Swap Christoph Hellwig
2001-11-20 21:05 ` Swap Steffen Persvold
2001-11-20 21:18 ` Swap Mike Fedyk
2001-11-20 21:33 ` Swap Nick LeRoy
2001-11-20 21:44 ` Swap Mike Fedyk
2001-11-20 22:00 ` Swap Nick LeRoy
2001-11-21 16:53 ` Swap Remco Post
2001-11-20 21:43 ` Swap Richard B. Johnson
2001-11-20 21:50 ` NFS, Paging & Installing [was: Re: Swap] Mike Fedyk
2001-11-21 1:22 ` Horst von Brand
2001-11-21 1:46 ` Mike Fedyk
2001-11-21 10:55 ` Trond Myklebust
2001-11-22 5:16 ` Bernd Eckenfels
2001-11-22 12:19 ` Trond Myklebust
2001-11-23 19:33 ` Mike Fedyk
2001-11-20 21:19 ` Swap Nick LeRoy
2001-11-21 16:48 ` Swap Remco Post
2001-11-20 20:58 ` Swap Mike Fedyk
2001-11-19 10:03 ` Swap Tim Connors
2001-11-19 10:16 ` Swap Dan Maas
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=20011018155636.B2467@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=greearb@candelatech.com \
--cc=jas88@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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