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

cl_max_dirty_pages not zeroed on startup

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Lustre 2.13.0, Lustre 2.12.1
    • Labels:
      None
    • Severity:
      3
    • Rank (Obsolete):
      9223372036854775807

      Description

      cl_dirty_max_pages (the internal representation of max_dirty_mb) is not zeroed at initialization.  The function client_adjust_max_dirty is called, but it only sets it if the value is <= 0, which will be true most of the time for random memory...  But not all of the time.

      So sometimes cl_max_dirty_pages ends up at some random positive value.  Easy fix.

        Attachments

          Activity

            People

            • Assignee:
              pfarrell Patrick Farrell
              Reporter:
              pfarrell Patrick Farrell
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: