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

truncate to DoM-file results in two RPCs

Details

    • Improvement
    • Resolution: Unresolved
    • Minor
    • Lustre 2.17.0
    • None
    • 9223372036854775807

    Attachments

      Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. LU-10509 sanity-dom test_fsx: FAIL: test_fsx failed with 110

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

        Activity

          [LU-11033] truncate to DoM-file results in two RPCs
          pjones Peter Jones made changes -
          Fix Version/s New: Lustre 2.17.0 [ 16192 ]
          Fix Version/s Original: Lustre 2.16.0 [ 15190 ]
          pjones Peter Jones made changes -
          Fix Version/s New: Lustre 2.16.0 [ 15190 ]
          Fix Version/s Original: Lustre 2.15.0 [ 14791 ]
          pjones Peter Jones made changes -
          Fix Version/s New: Lustre 2.15.0 [ 14791 ]
          Fix Version/s Original: Lustre 2.14.0 [ 14490 ]
          jgmitter Joseph Gmitter (Inactive) made changes -
          Fix Version/s New: Lustre 2.14.0 [ 14490 ]
          Fix Version/s Original: Lustre 2.13.0 [ 14290 ]
          jgmitter Joseph Gmitter (Inactive) added a comment -

          This ticket remains open to improve the truncation already implemented.

          jgmitter Joseph Gmitter (Inactive) added a comment - This ticket remains open to improve the truncation already implemented.
          jgmitter Joseph Gmitter (Inactive) made changes -
          Fix Version/s New: Lustre 2.13.0 [ 14290 ]
          tappro Mikhail Pershin made changes -
          Link New: This issue is related to LU-10509 [ LU-10509 ]
          jgmitter Joseph Gmitter (Inactive) made changes -
          Labels New: DoM2
          tappro Mikhail Pershin added a comment -

          if truncate size is in DoM range then SETATTR is not needed because there will be truncate. I think it is safe to check that on client and decide to send setattr or not

          tappro Mikhail Pershin added a comment - if truncate size is in DoM range then SETATTR is not needed because there will be truncate. I think it is safe to check that on client and decide to send setattr or not
          bzzz Alex Zhuravlev added a comment -

          this is not good on its own - two sync RPCs instead of one. but also breaks optimisation in osd_punch() as we can't skip truncate to existing i_size.

          bzzz Alex Zhuravlev added a comment - this is not good on its own - two sync RPCs instead of one. but also breaks optimisation in osd_punch() as we can't skip truncate to existing i_size.

          People

            tappro Mikhail Pershin
            bzzz Alex Zhuravlev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: