Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-12388

expand QUOTA_MAX_TRANSIDS for Project Quota?

Details

    • Question/Request
    • Resolution: Won't Fix
    • Trivial
    • None
    • Lustre 2.10.7
    • None
    • 9223372036854775807

    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?

      Attachments

        Issue Links

          Activity

            [LU-12388] expand QUOTA_MAX_TRANSIDS for Project Quota?

            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.

            wshilong Wang Shilong (Inactive) added a comment - 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.

            People

              wshilong Wang Shilong (Inactive)
              takamura Tatsushi Takamura
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: