public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Stan Hoeppner <stan@hardwarefreak.com>, xfs@oss.sgi.com
Subject: Re: Enforcing quota for root user
Date: Wed, 12 Nov 2014 09:32:03 +1100	[thread overview]
Message-ID: <20141111223203.GS28565@dastard> (raw)
In-Reply-To: <631A9090-F9FE-4B8E-88CD-1B30CAFC65B7@colorremedies.com>

On Tue, Nov 11, 2014 at 11:00:25AM -0700, Chris Murphy wrote:
> 
> On Nov 11, 2014, at 8:36 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> 
> > On 11/11/2014 04:22 AM, Cyril Scetbon wrote:
> >> That's what I've read first, but someone showed me a sample where it works. He just told me he was using project quota. However, does it make sense ? 
> >> I've also read somewhere else that quota is never enforced for root user (id,gid=0) that's why I was testing it ....
> > 
> > No, it doesn't make sense.  Why would you want to enforce quotas for root?
> 
> A week ago I tried this and project quotas appear to apply to root.

By intent and design. Project quotas are not a user/group based
quota and so there is no exemption for any user.

> [root@localhost project_quota_test1]# xfs_quota -c df
> Filesystem           1K-blocks       Used  Available  Use% Pathname
> /dev/sdb              83845120     157980   83687140    0% /xfs_local
> /dev/sdb                102400     124928 9223372036854753280  122% /xfs_local/project_quota_test1
> [root@localhost project_quota_test1]# dd if=/dev/zero of=test100MB bs=1M count=100
> dd: error writing ‘test100MB’: No space left on device
> 79+0 records in
> 78+0 records out
> 81788928 bytes (82 MB) copied, 0.163849 s, 499 MB/s
> [root@localhost project_quota_test1]# xfs_quota -c df
> Filesystem           1K-blocks       Used  Available  Use% Pathname
> /dev/sdb              83845120     237748   83607372    0% /xfs_local
> /dev/sdb                102400     204800 9223372036854673408  200% /xfs_local/project_quota_test1

It's gone negative. That number in hex: 0x7FFFFFFFFFFE7000

What kernel are you using, and can you outline all the way you set
everything up to cause that to occur? Also, what is the output of a
plain 'df -h' when it is in that state?

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-11-11 22:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 22:46 Enforcing quota for root user Cyril Scetbon
2014-11-11  6:56 ` Stan Hoeppner
2014-11-11 10:22   ` Cyril Scetbon
2014-11-11 15:36     ` Stan Hoeppner
2014-11-11 18:00       ` Chris Murphy
2014-11-11 22:32         ` Dave Chinner [this message]
2014-11-11 22:36           ` Eric Sandeen
2014-11-11 23:34             ` Dave Chinner
2014-11-11 23:35           ` Chris Murphy
2014-11-12  0:09             ` Dave Chinner
2014-11-12 13:55       ` Cyril Scetbon

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=20141111223203.GS28565@dastard \
    --to=david@fromorbit.com \
    --cc=lists@colorremedies.com \
    --cc=stan@hardwarefreak.com \
    --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