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

errors not propagated to changelog readers

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.11.0
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      Reviewing https://review.whamcloud.com/#/c/29818/ I noticed that errors are not being propagated to changelog readers. I suggest that crs_err be changed to int and the errno associated to any errors encountered be stored there. Then this value can be used in chlg_read() if no records were emitted. Also the return value of chld_load() will also be the return value of kthread_stop() in chlg_release(). clhg_release() should save and return any errors there too.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-10379 "lfs changelog" generates constant "Changelog: Input/output error" errors

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              wc-triage WC Triage
              jhammond John Hammond
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: