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

lockless IO stucks if client has other lock already

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      lockless write IO may stuck if client has other lock on the same page, e.g. PR lock from previous READ or GLIMPSE requests. WRITE IO cause blocking AST from server for that PR lock which tries to discard pages on client and stuck on cl_page_own() forever if that page is involved in lockless WRITE already.

      At first sign it seems that any lockless write must find and cancel all client locks on write range before IO is started. Though can be not enough because some other concurrent lock can be taken while lockless IO is being issued.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-11435 add contention check and accounting for IBITS locks

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

          Activity

            People

              paf0186 Patrick Farrell (Inactive)
              tappro Mikhail Pershin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: