Hello aldyth.m,

There is an issue in OneFS 7.2.0.1 where Quota enforcement may be incorrectly changed when your quota is edited through the OneFS Web Administration Interface. In some cases, the quota will become "not enforced" or simply an Accounting Quota. To verify this, please log in to the OneFS CLI and check your quota setting (in my example, the path is a test directory called /ifs/data/ktjoh):

**On you cluster, please replace the quota path with the relevant path you are looking in to.**

seven201-1# isi quota quotas list --path=/ifs/data/ktjoh -v

Type      AppliesTo  Path  Snap  Hard  Soft  Adv  Grace  Files  With Overhead  W/O Overhead  Over  Enforced Container  Linked

-----------------------------------------------------------------------------------------------------------------------------------------

directory DEFAULT    /ifs/data/ktjoh  No    -     -     -    -      1      2.00K  30.00b        -     No        No         -

-----------------------------------------------------------------------------------------------------------------------------------------

Note, in this example, I changed my quota in the WebUI and my quota is no longer enforced. The enforced flag can be set via CLI with these steps:

seven201-1# isi quota quotas modify --path=/ifs/data/ktjoh --type=directory --enforced=yes

seven201-1# isi quota quotas list --path=/ifs/data/ktjoh -v

Type AppliesTo Path Snap Hard Soft Adv Grace Files With Overhead W/O Overhead Over Enforced Container Linked

--------------------------------------------------------------------------------------------------------------------------------------------

directory DEFAULT /ifs/data/ktjoh No 50.00M - - - 7 705.50M 705.00M 655.00M Yes No -

--------------------------------------------------------------------------------------------------------------------------------------------

Total: 1

At this point, my quota will be enforced again; however, you should run a QuotaScan job to ensure it is always being properly applied:

seven201-1# isi job start quotascan

The permanent fix for this issue is currently scheduled for a Maintenance Release (MR) of OneFS 7.2. If this issue does occur, the only current workaround is to administer the quotas via the CLI (i.e. reset enforcement OR all administration to avoid any unwanted changes.) If you are still having issues with your quota after this setting is changed, please reply to this post with your quota settings and I can look in to it for you!