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

upgrade to Lustre 2.10 breaks quota if project quota is not enabled

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Not a Bug
    • Affects Version/s: Lustre 2.10.0
    • Fix Version/s: None
    • Labels:
      None
    • Severity:
      3
    • Rank (Obsolete):
      9223372036854775807

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                wangshilong Wang Shilong (Inactive)
                Reporter:
                adilger Andreas Dilger
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: