[LU-150] inaccurate quota output after the recovery

• Type: Bug
• Resolution: Won't Fix
• Priority: Blocker
• Fix Version/s: Lustre 1.8.6
• Affects Version/s: Lustre 1.8.6
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Shuichi Ihara (Inactive)

Description

We can't see correct quota output after the recovery. Once run quotacheck again, the 'lfs quota' shows right output. Here is quick reproducer. We confirmed same situation happens on both lustre-1.8.4 and lustre-1.8.5.

0. Normal case
It's no problem.

[test@r03 test]$ lfs quota -u test /mnt/lustre
Disk quotas for user test (uid 501):
Filesystem kbytes quota limit grace files quota limit grace
/mnt/lustre 4 0 0 - 1 0 0 -

1. 'lfs quota' on during the recovery
Umount/mount an OST and occurs the recovery. The during the recovery, when we run 'lfs quota' command, the some data are inaccurate.

Disk quotas for user test (uid 501):
Filesystem kbytes quota limit grace files quota limit grace
/mnt/lustre [0] 0 0 - [0] 0 0 -
Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate.

2. 'lfs quota' after the recovery

Even after finish the recovery, inaccurate output still can't fixed.

Disk quotas for user test (uid 501):
Filesystem kbytes quota limit grace files quota limit grace
/mnt/lustre [0] 0 0 - [0] 0 0 -
Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate.

3. run quotacheck again

the correct output shows up once we run quotacheck again after the recovery.

Disk quotas for user test (uid 501):
Filesystem kbytes quota limit grace files quota limit grace
/mnt/lustre 4 0 0 - 1 0 0 -

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