From: Dave Chinner <david@fromorbit.com>
To: Jerzy Borkowski <jubork@ncac.torun.pl>
Cc: xfs@oss.sgi.com
Subject: Re: project quota: df/reservations
Date: Sat, 5 Feb 2011 08:27:50 +1100 [thread overview]
Message-ID: <20110204212750.GA11040@dastard> (raw)
In-Reply-To: <4D4BF051.9000608@ncac.torun.pl>
On Fri, Feb 04, 2011 at 01:25:53PM +0100, Jerzy Borkowski wrote:
> Hello,
>
> 1) Fancy a project with quota set to 10GB, and filled
> with 5GB of data. When I type
>
> df /path/to/project/tree
>
> it shows 5GB free space. Now, the root user
> fills up the disk (outside project tree), so the
> XFS filesystem is really 100% full. The df command
> still shows 5GB free space. I guess, this is
> intentional. I propose to add some switch/flag
> (either during mount or project creation),
> which would tell XFS to report in statfs() calls
> the free space as: min(project_free_space, filesystem_free_space).
If you just run "df" or "df /path/to/mtpt" rather than asking
specifically for the project tree path, you should see the real
filesystem usage.
Think of project quotas like thin provisioned filesystems - they can
still have space available when the underlying storage runs out and
it is up to the admin to manage this situation.
> 2) is there any way to have space reservations for projects (like in ZFS) ?
> For instance, a project with 10GB quota and 7GB of preallocated
> space, so even root, writing outside the project tree, cannot
> completely fill up the disk.
No. Quotas can only be used to limit space usage, not reserve it.
It could probably be done, but it's not a simple retrofit...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-04 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 12:25 project quota: df/reservations Jerzy Borkowski
2011-02-04 21:27 ` Dave Chinner [this message]
2015-05-19 14:53 ` inode64 Jerzy Borkowski
2015-05-19 15:05 ` inode64 Carlos Maiolino
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=20110204212750.GA11040@dastard \
--to=david@fromorbit.com \
--cc=jubork@ncac.torun.pl \
--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