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

llog_process_thread() may use wrong offset for the next block

    XMLWordPrintable

Details

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

    Description

      the llog_process_thread() save curent offset in last_offset variable before getting the new block of data, and uses it as the beginning of that block later. That can be wrong because new block can be read from different offset, depending on index being searched. We need to use the value returned by llog_next_block() call.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-6944 LBUG: (osp_sync.c:1139:osp_sync_thread()) ASSERTION( thread->t_flags != SVC_RUNNING ) failed: 806 changes, 230 in progress, 7 in flight

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. LU-9312 HSM coordinator llog scalability

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

          Bug - A problem which impairs or prevents the functions of the product. LU-5635 (llog.c:310:llog_process_thread()) ASSERTION( index <= last_index + 1 ) failed:

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              tappro Mikhail Pershin
              tappro Mikhail Pershin
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: