All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Weird behaviour with project quotas
Date: Sat, 30 Nov 2024 09:14:20 +1100	[thread overview]
Message-ID: <Z0o8vE4MlIg-jQeR@dread.disaster.area> (raw)
In-Reply-To: <20241129103332.4a6b452e@harpe.intellique.com>

On Fri, Nov 29, 2024 at 10:33:32AM +0100, Emmanuel Florac wrote:
> Le Fri, 29 Nov 2024 08:07:09 +1100
> Dave Chinner <david@fromorbit.com> écrivait:
> 
> > > As far as I understand, and from my tests, on folders on which a
> > > project quota is applied, either the available quota or the actually
> > > avialable space should be reported when using "df".  
> > 
> > Only if you are using project quotas as directories quotas. i.e.
> > the directory you are querying with df needs to have the
> > XFS_DIFLAG_PROJINHERIT flag set on it for df to behave this way.
> 
> Interesting, and how is this set ? I basically set up quotas using
> something like
> 
> xfs_quota -x -c 'project -s -p /mnt/raid/project1 10' /mnt/raid
> 
> xfs_quota -x -c "limit -p bhard=30000g 10" /mnt/raid

That should set it up appropriately, hence the need to check if it
has actually been set up correctly on disk.

> > > However on a
> > > running system (Debian 12, kernel 6.1 Debian) I have incoherent
> > > results:  
> > 
> > 32 bit or 64 bit architecture?
> 
> AMD64, the most common one.
>  
> > > The volume /mnt/raid is 100 TB and has 500GB free.
> > > 
> > > There are several folders like /mnt/raid/project1,
> > > /mnt/raid/project2 etc with various quotas (20TB, 30TB, etc).  
> > 
> > Output of df and a project quota report showing usage and limits
> > would be useful here.
> > 
> > Then, for each of the top level project directories you are querying
> > with df, also run `xfs_io -rxc "stat" <dir>` and post the output.
> > This will tell us if the project quota is set up correctly for df to
> > report quota limits for them.
> > 
> > It would also be useful to know if the actual quota usage is correct
> > - having the output of `du -s /mnt/raid/project1` to count the
> > blocks and `find /mnt/raid/project1 -print |wc -l` to count the
> > files in quota controlled directories. That'll give us some idea if
> > there's a quota accounting issue.

iAnother thought occurred to me - can you also check that
/etc/projid and /etc/projects is similar on all machines, and post
the contents of them from the bad machine?

> OK, I'll run these as soon as I have a connection to the system. There
> seemed to be no error with the reported used space though, only
> available remaining space in quota'ed directories; however df reports
> actually available space for directories without quota set.

Ok - it would be helpful to post the commands you run and the output
so that we both know exactly what behaviour you are seeing.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2024-11-29 22:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 16:14 Weird behaviour with project quotas Emmanuel Florac
2024-11-28 21:07 ` Dave Chinner
2024-11-29  9:33   ` Emmanuel Florac
2024-11-29 22:14     ` Dave Chinner [this message]
2024-12-12 15:33       ` Emmanuel Florac
2024-12-12 20:25         ` Darrick J. Wong
2024-12-13 15:42           ` Emmanuel Florac
2024-12-13 17:15             ` Darrick J. Wong
2024-12-16 22:18               ` Emmanuel Florac
2024-12-17 16:50                 ` Darrick J. Wong
2024-12-18 17:47                   ` Emmanuel Florac
2024-12-18 17:55                     ` 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=Z0o8vE4MlIg-jQeR@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=eflorac@intellique.com \
    --cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.