Multiple users blocked by phantom quota after temporary hostname change

[belenisla]

Hello,

We are running BeeGFS 7.3.3 and several users are blocked by quota enforcement, even though beegfs-ctl --getquota shows they have not exceeded their quotas.

We suspect this may have happened after a temporary hostname change on all servers, although we were able to restart the BeeGFS services by copying originalNodeID to nodeID. The hostnames have now been reverted to their original names, but the problem persists.

So far, we have tried setting quotaEnableEnforcement=false in the configuration files of meta, storage, and mgmtd. After switching it back to true, running beegfs-fsck --enablequota, and restarting all BeeGFS services, the phantom quota issue still occurs.

My questions are:

Could this issue have been caused by the hostname change, or could the origin be something else?

Is there any way to fix or reset the quota enforcement flags without losing data?

Thank you for any guidance!