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

Reads are not included in IO accounting

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.11.0, Lustre 2.10.3
    • Lustre 1.8.7, Lustre 1.8.6
    • None
    • Linux, Lustre b1_8
    • 3
    • 24,536
    • 9730

    Description

      Writes are accounted for, but not reads. The supplied patch fixes this.

      It seems that the accounting it normally done in the kernels page writeback and readahead
      functionality. Therefore as Lustre implements its own readahead, it must also maintain its own
      accounting on reads (but not writes).

      Previously discussed in:

      Attachments

        Issue Links

          Activity

            [LU-618] Reads are not included in IO accounting
            mdiep Minh Diep made changes -
            Labels Original: LTS
            mdiep Minh Diep made changes -
            Fix Version/s New: Lustre 2.10.3 [ 13591 ]
            pjones Peter Jones made changes -
            Labels New: LTS
            pjones Peter Jones made changes -
            Fix Version/s New: Lustre 2.11.0 [ 13091 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            adilger Andreas Dilger made changes -
            Description Original: Writes are accounted for, but not reads. The supplied patch fixes this.

            It seems that the accounting it normally done in the kernels page writeback and readahead
            functionality. Therefore as Lustre implements its own readahead, it must also maintain its own
            accounting on reads (but not writes).

            Previously discussed in:

            * http://lists.lustre.org/pipermail/lustre-devel/2011-April/003767.html
            * https://bugzilla.lustre.org/show_bug.cgi?id=24536
            New: Writes are accounted for, but not reads. The supplied patch fixes this.

            It seems that the accounting it normally done in the kernels page writeback and readahead
            functionality. Therefore as Lustre implements its own readahead, it must also maintain its own
            accounting on reads (but not writes).

            Previously discussed in:

            * http://lists.lustre.org/pipermail/lustre-devel-lustre.org/2011-April/001586.html
            * https://bugzilla.lustre.org/show_bug.cgi?id=24536
            pjones Peter Jones made changes -
            Assignee Original: Peter Jones [ pjones ] New: Hongchao Zhang [ hongchao.zhang ]
            pjones Peter Jones made changes -
            Assignee Original: Robert Read [ rread ] New: Peter Jones [ pjones ]
            mark Mark Hills created issue -

            People

              hongchao.zhang Hongchao Zhang
              mark Mark Hills
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: