[LU-12388] expand QUOTA_MAX_TRANSIDS for Project Quota?

• Status: Closed
• Project: Lustre
• Affects Version/s: Lustre 2.10.7
• Type: Question/Request
• Priority: Trivial
• Reporter: Tatsushi Takamura
• Assignee: Wang Shilong (Inactive)
• Resolution: Won't Fix

Description

lustre/include/lustre_quota.h

/* With the DoM, both inode quota in meta pool and block quota in data pool
 * will be enforced at MDT, there are at most 4 quota ids being enforced in
 * a single transaction for inode and block quota, which is chown transaction:
 * original uid and gid, new uid and gid.
 *
 * This value might need to be revised when directory quota is added.  */

#define QUOTA_MAX_TRANSIDS    8

 

 According to the comment, it appears that QUOTA_MAX_TRANSIDS need to consider projid for PROJECT QUOTA( though chown doesn't change projid).
Because there are no operation that changes uid, gid, and projid in a single transaction, is it OK that QUOTA_MAX_TRANSIDS is 8? Or is there any operations that need more than 8 qids for a single transaction?

Issue Links

• is related to: LU-15193 qsd_op_begin: more than 8 qids enforc...

Comments

[Wang Shilong (Inactive)]

Yup, i was not aware of any operations could change them at the same time, we could fix it if that is needed in the future if that is needed.