Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • None
    • 8
    • 3
    • 7149

    Description

      from LU-1382 The workaround we have consist of removing quota (-b 0 -B 0 -i 0 -I 0) then re-applying them, user by user, but it would be better if quota were automatically propagated during add of new OSTs or, at least, handled by a quotacheck.
      After a filesystem extension (ie add of new OSTs), quota are not propagated on newer OSTs.
      Running quotacheck, quotaoff or quotaon doesn't change anything to the picture.

      Attachments

        Activity

          [LUDOC-65] add quota workaround to manual (Ch 21)

          Fix approved and merged.

          linda Linda Bebernes (Inactive) added a comment - Fix approved and merged.

          Second patch submitted and ready for review at http://review.whamcloud.com/#/c/7540/

          linda Linda Bebernes (Inactive) added a comment - Second patch submitted and ready for review at http://review.whamcloud.com/#/c/7540/
          linda Linda Bebernes (Inactive) added a comment - Change ready for review at http://review.whamcloud.com/#/c/7540/

          yes, this workaround is only needed for old quota architecture (< 2.4).

          niu Niu Yawei (Inactive) added a comment - yes, this workaround is only needed for old quota architecture (< 2.4).

          Niu or Johann, can you please confirm Richard's comments above?

          adilger Andreas Dilger added a comment - Niu or Johann, can you please confirm Richard's comments above?

          I've been discussing this topic with Linda: The Manual currently covers the entire 2.x series of Lustre.

          I understand this workaround becomes redundant for Lustre 2.4 an beyond. A suitable update to the Manual should include the workaround described here, prepended with something like:

          <note condition='l24'><para>This workaround is only needed for versions of Lustre before 2.4 as the bug was fixed in the 2.4 release</para></note>
          
          rhenwood Richard Henwood (Inactive) added a comment - I've been discussing this topic with Linda: The Manual currently covers the entire 2.x series of Lustre. I understand this workaround becomes redundant for Lustre 2.4 an beyond. A suitable update to the Manual should include the workaround described here, prepended with something like: <note condition='l24'><para>This workaround is only needed for versions of Lustre before 2.4 as the bug was fixed in the 2.4 release</para></note>

          People

            cliffw Cliff White (Inactive)
            cliffw Cliff White (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: