Le Sat, 30 Nov 2024 09:14:20 +1100
Dave Chinner <david@xxxxxxxxxxxxx> é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:
pgplERwADuqd3.pgp
Description: Signature digitale OpenPGP
