XFS Project Quota Metadata Remains on Host After Multiple PVC Create/Delete Cycles

[laik]

Problem Description:

After repeatedly creating and deleting PersistentVolumeClaims (PVCs) in Kubernetes, some XFS project quota metadata remains on the host filesystem and is not automatically cleaned up. As a result, xfs_quota still reports project IDs and quota limits even though the corresponding PVCs have already been removed.

Example inspection:

xfs_quota -x -c "report -p" /var/openebs/local
Project quota on /var/openebs/local (/dev/sda1)
                               Blocks                     
Project ID       Used       Soft       Hard    Warn/Grace     
---------- -------------------------------------------------- 
#0                  0          0          0     00 [--------]
#1                  0     102400     102400     00 [--------]
#2                  0     102400     102400     00 [--------]

Listing the local volume directory still shows project IDs:

ls /var/openebs/local
pvc-d5696ee0-8514-481a-bed7-f85c7d7ff14e

xfs_io -c "stat" /var/openebs/local/pvc-d5696ee0-8514-481a-bed7-f85c7d7ff14e
...
fsxattr.projid = 2

This indicates that the project quota and project ID mapping were not cleaned up properly after PVC deletion.