[LU-16857] Allocate OST objects from spill pool when pool quota exceeded Created: 30/May/23  Updated: 30/May/23

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.14.0, Lustre 2.16.0, Lustre 2.15.0
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Andreas Dilger Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Related
is related to LU-13058 Intermediate component removal (PFL/SEL) Open
is related to LU-11023 OST Pool Quotas Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 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. It would be possible for them to change the default layout for all of their direvtories, but it would need to be changed back once they are below quota again, which is inconvenient.

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.


Generated at Sat Feb 10 03:30:35 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.