[LU-9554] upgrade to Lustre 2.10 breaks quota if project quota is not enabled

• Type: Bug
• Resolution: Not a Bug
• Priority: Critical
• Affects Version/s: Lustre 2.10.0
• Severity: 3
• Assignee: Wang Shilong (Inactive)
• Reporter: Andreas Dilger

Description

I was reading in the Lustre manual section for project quota:

Lustre filesystem formatted with a Lustre release prior to 2.10 can be still safely upgraded to release 2.10, but will not have functional space usage report until tune2fs --project is run against all targets. This command sets the PROJECT feature flag in the superblock and runs e2fsck (as a result, the target must be offline) to build the per-PROJID disk usage database.

This doesn't make sense to me. Does this mean that quota is broken on Lustre until "tune2fs --project" is enabled (i.e. that feature HAS to be enabled)? Or is it only that project quota is not working until "tune2fs --project" is run on all targets?

If project quota HAS to be enabled for regular quota to work, I would consider that a defect that needs to be fixed before the 2.10 release. If project quota is not enabled on the targets, then the regular user/group quota should continue to work normally on an upgraded system, especially since this would otherwise prevent a system from being downgraded to an older version of Lustre/ldiskfs that doesn't support the project quota feature.

Issue Links

• is related to: LU-10857 sanity-quota fix: allow to disable project quotas
• is related to: LU-4017 Add project quota support feature
• is related to: LUDOC-202 Lustre Manual Documentation for project quota feature
• is related to: LU-7991 Add project quota for ZFS

Comments

[Peter Jones]

Thanks for the quick clarification Wang Shilong

[Wang Shilong (Inactive)]

Hi Andreas,

Sorry, my Manaul updates are confusing, of course usr/group quota could be worked without problems
even project quota feature disabled in default, it should point out that only affect project quota.

Lustre filesystem formatted with a Lustre release prior to 2.10 can be still safely upgraded to release 2.10, but will not have project functional space usage report until tune2fs --project is run against all targets. This command sets the PROJECT feature flag in the superblock and runs e2fsck (as a result, the target must be offline) to build the per-PROJID disk usage database.

[Andreas Dilger]

If my understanding of the description in the manual is incorrect, then I'm happy to close this ticket. In that case, the description of enabling project quota on the servers should be changed in the user manual.