From: Emmanuel Florac <eflorac@intellique.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Weird behaviour with project quotas
Date: Thu, 12 Dec 2024 16:33:51 +0100 [thread overview]
Message-ID: <20241212163351.58dd1305@harpe.intellique.com> (raw)
In-Reply-To: <Z0o8vE4MlIg-jQeR@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 3992 bytes --]
Le Sat, 30 Nov 2024 09:14:20 +1100
Dave Chinner <david@fromorbit.com> écrivait:
> > 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.
>
Unfortunately in the meantime the users did some cleanup, therefore the
displayed information is coherent again (as there is more free space on
the filesystem as a whole as any remaining allocated quota).
xfs_quota -x -c "report -p"
Project quota on /mnt/raid (/dev/mapper/vg0-raid)
Blocks
Project ID Used Soft Hard Warn/Grace
----------- ------------------------------------------------------
<snip>
#40 10795758244 0 16106127360 00 [--------]
> > > Output of df and a project quota report showing usage and limits
> > > would be useful here.
looking at the corresponding folder :
/dev/mapper/vg0-raid 15T 11T 5,0T 68% /mnt/raid/pad
du -s /mnt/raid/pad
10795758244 /mnt/raid/pad
# find /mnt/raid/pad -print | wc -l
39086
> > > 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.
> > >
Starting with "pad" :
# xfs_io -rxc "stat" pad
fd.path = "."
fd.flags = non-sync,non-direct,read-only
stat.ino = 6442662464
stat.type = directory
stat.size = 4096
stat.blocks = 16
fsxattr.xflags = 0x200 \[--------P--------\]
fsxattr.projid = 40
fsxattr.extsize = 0
fsxattr.cowextsize = 0
fsxattr.nextents = 2
fsxattr.naextents = 0
dioattr.mem = 0x200
dioattr.miniosz = 512
dioattr.maxiosz = 2147483136
# xfs_io -rxc "stat" rush
fd.path = "."
fd.flags = non-sync,non-direct,read-only
stat.ino = 142
stat.type = directory
stat.size = 283
stat.blocks = 0
fsxattr.xflags = 0x200 \[--------P--------\]
fsxattr.projid = 10
fsxattr.extsize = 0
fsxattr.cowextsize = 0
fsxattr.nextents = 0
fsxattr.naextents = 0
dioattr.mem = 0x200
dioattr.miniosz = 512
dioattr.maxiosz = 2147483136
# xfs_io -rxc "stat" labo
fd.path = "."
fd.flags = non-sync,non-direct,read-only
stat.ino = 2147695168
stat.type = directory
stat.size = 310
stat.blocks = 0
fsxattr.xflags = 0x200 \[--------P--------\]
fsxattr.projid = 20
fsxattr.extsize = 0
fsxattr.cowextsize = 0
fsxattr.nextents = 0
fsxattr.naextents = 0
dioattr.mem = 0x200
dioattr.miniosz = 512
dioattr.maxiosz = 2147483136
# xfs_io -rxc "stat" prods
fd.path = "."
fd.flags = non-sync,non-direct,read-only
stat.ino = 4295178816
stat.type = directory
stat.size = 319
stat.blocks = 0
fsxattr.xflags = 0x200 \[--------P--------\]
fsxattr.projid = 30
fsxattr.extsize = 0
fsxattr.cowextsize = 0
fsxattr.nextents = 0
fsxattr.naextents = 0
dioattr.mem = 0x200
dioattr.miniosz = 512
dioattr.maxiosz = 2147483136
> > > 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?
>
Hum, actually they didn't set up neither projid nor projects. Of course
I did create these during my tests, but could this be the culprit ?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
------------------------------------------------------------------------
https://intellique.com
+33 6 16 30 15 95
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-12-12 15:41 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
2024-12-12 15:33 ` Emmanuel Florac [this message]
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=20241212163351.58dd1305@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=david@fromorbit.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.