From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Cc: Theodore Ts'o <tytso@mit.edu>, Ben Myers <bpm@sgi.com>,
Dmitry Monakhov <dmonakhov@openvz.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: Re: [RFC] directory quota survey on xfs
Date: Mon, 23 Dec 2013 10:12:19 +0100 [thread overview]
Message-ID: <201312231012.19204.arekm@maven.pl> (raw)
In-Reply-To: <20131223014222.GC3220@dastard>
On Monday 23 of December 2013, Dave Chinner wrote:
> > As always, any comment or idea are welcome.
>
> I'd suggest that you implement project quotas, not directory quotas.
> They are way more flexible than pure directory quotas, but with only
> a few lines of code and a special directory flag they can be used to
> > implement directory subtree quotas....
Would be also nice to allow a file to belong to more than one project.
Let say I want to have
/projects/ with 10GB quota
and
/projects/projectA/ with 1GB quota
/projects/projectB/ with 2GB quota
and so on that's still limited by /projects/ 10GB quota limit.
(and can't use user/group quota for that since the files belong to various
users/groups)
--
Arkadiusz Miśkiewicz, arekm / maven.pl
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-23 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 9:59 [RFC] directory quota survey on xfs Zheng Liu
2013-12-23 1:42 ` Dave Chinner
2013-12-23 9:12 ` Arkadiusz Miśkiewicz [this message]
2013-12-23 23:43 ` Dave Chinner
2014-01-15 8:12 ` Zheng Liu
2014-01-15 18:03 ` Andreas Dilger
2014-01-15 21:32 ` Dave Chinner
2014-01-21 7:07 ` Zheng Liu
2014-01-23 22:32 ` Dave Chinner
2014-01-24 0:06 ` Darrick J. Wong
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=201312231012.19204.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=adilger.kernel@dilger.ca \
--cc=bpm@sgi.com \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.com \
/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).