[LU-16857] OST object allocation should not select OSTs/pools where quota is exceeded

• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.14.0, Lustre 2.16.0, Lustre 2.15.0
• Severity: 3
• Assignee: WC Triage
• Reporter: Andreas Dilger

Description

In cases where PFL layouts include a flash component at the start of the file to handle small files, and if the user runs out of pool quota on the flash OSTs then the filesystem becomes almost unusable for them, even if they have quota remaining on the disk pool. Similarly, if a user/group/project has consumed all available qunits, the MDS should avoid allocating new objects for that UID/GID/PROJID on OSTs that have no more free blocks.

When allocating OST objects for a component that has specified an OST pool, but the user has exceeded their OST pool quota, the objects should be allocated from the spill pool, if it is configured. Otherwise, the MDS will allocate OST objects that the user cannot write without getting EDQUOT.

Issue Links

• is related to: LU-11023 OST Pool Quotas
• is related to: LU-9 Optimize weighted QOS Round-Robin allocator
• is related to: LU-19567 lfs-setquota.1: document minimum qunit limits in man page
• is related to: LU-18022 DNE3: client to retry on other MDT if mkdir returns EDQUOT
• is related to: LU-18222 LQA: Implement quota aggregation limits by ID range
• is related to: LU-9 Optimize weighted QOS Round-Robin allocator
• is related to: LU-13058 Intermediate component removal (PFL/SEL)