After deleting the limits with "-delete" option the LQE doesn't have any limits and it is expected that default limits should be enforced for such LQE. However, default limits are not applied for such LQE and it is proceeding unlimited:

[root@vm4 tests]# lfs setquota -u quota_usr -B1G /mnt/lustre
[root@vm4 tests]# lfs setquota -u quota_usr --delete /mnt/lustre
[root@vm4 tests]# lfs setquota -U -B2G /mnt/lustre
[root@vm4 tests]# lfs quota -u quota_usr /mnt/lustre
Disk quotas for usr quota_usr (uid 1000):
      Filesystem  kbytes   bquota  blimit  bgrace   files   iquota  ilimit  igrace
     /mnt/lustre       0        0       0       -       0        0       0       - 

I think the problem appears because after deleting the lqe it continues to present in an lqe_hash. Ideally after deleting we should apply default quota limits and notify quota slaves about that.

hongchao.zhang , adilger , does it sound like a problem? I think from the admins point of view after applying default quotas we shouldn't have not enforced LQEs besides for which we set 0 limits intentionally:

• unlimited: limits set to 0
• personal limits: limits set to X > 0
• default limits - for other cases