[LU-1438] quota_chk_acq_common() still haven't managed to acquire quota

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Fix Version/s: Lustre 2.3.0, Lustre 2.1.4, Lustre 1.8.9
• Affects Version/s: Lustre 1.8.7
• Environment: lustre-1.8.7-wc1, RHEL5.7 for servers, RHEL6.2 for clients
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Shuichi Ihara (Inactive)

Description

we are getting some of quota related problem. the quota feature is enabled on the filesystem and the customer changed group name to the many big files, then ran lfs quotacheck command.
After that, even the group didn't exceed the quota limitation, they got the disk quota exceeded messages.

OSS/MDS side, the following messages showed up since changed group name.
(quota_interface.c:473:quota_chk_acq_common()) still haven't managed to
acquire quota space from the quota master after 20 retries (err=0, rc=0)

It seems to be close to LU-428.

Issue Links

• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA

Comments

[Peter Jones]

ok thanks Ihara

[Shuichi Ihara (Inactive)]

this might be caused by LU-1584 and LU-1720. Please close this ticket.
I will open new ticket if we see same issue after apply LU-1438 and LU-1720 patches.

[Shuichi Ihara (Inactive)]

We didn't apply patches yet, but will apply them on the next scheduled maintenance time.

[Niu Yawei (Inactive)]

probably, is there anything useful from the debug log?

[Shuichi Ihara (Inactive)]

This might be related to 32bit quota setting limitation?

[Shuichi Ihara (Inactive)]

Hi Niu,

Thanks for this debug patch. I will ask customer if we can apply patch.

[Niu Yawei (Inactive)]

Hi, Ihara

Could you apply this debug patch? then we'll see lots more deubug information in the syslong along with the "still can't acquire..." messages. Thanks.

[Shuichi Ihara (Inactive)]

Hi Niu,

uploaded debug files on uploads/LU-1438/debugfile.20120628.gz
However, it's not easy to reproduce this messages though the messages still showed up on the system log file irregularly.
The lustre debug file doesn't contain messages. perhaps, the maximum debug size (100MB) exceeded quickly?
Any ideas to keep track and debug information in this situation?

[Niu Yawei (Inactive)]

Hi, Ihara

The debug patch would be similar to enable D_TRACE & D_QUOTA for debug log, If the cusotmer can't affort D_TRACE debug log, we can only enable D_QUOTA first to collect some debug log.

The 28760 is pid, and the 0 is 'extern pid' (looks it's always 0 for now, you can just ignore it).

[Shuichi Ihara (Inactive)]

Niu, I meant you could make debug patch to see more detail information during the production system. e.g) Who exceed quota limit by this messages. surely, we didn't do any operations (set/clear quota) when the following messages showed up.

Jun 25 03:03:59 nos141i kernel: Lustre: 28760:0:(quota_interface.c:481:quota_chk_acq_common()) still haven't managed to acquire quota space from the quota master after 10 retries (err=0, rc=0)

We don't know how reproduce this problem at this morment, but let me ask we can enable debug flags. BTW, what is "28760:0" of above messages?