Uquota incorrectly reports quota in some cases closed
We have updated uquota to work with the new custom directory names.
One issue remains: uquota sometimes reports the default quota, even when the project has a higher quota approved in SUPR. This affects only the output of uquota, and not the project.
If you hit this remaining issue, a workaround is to run lfs quota. For example, if my project is snic20209999, I run:
lfs quota -h -g snic20209999 /crex
We are working on a fix.
Update 2021-10-18 14:00
We have now updated uquota
with support for directory names.
Please contact the support if you have any questions or if you run
into issues.
Affected systems: rackham and snowy
Written by Support Team on