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

open-close operation can lead to loss of file time set performed in the middle

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • Lustre 2.16.0
    • None
    • None
    • 9223372036854775807

    Description

      the original request in LU-12026 was to update *time as a part of LSOM update, i.e. to be stored in LSOM ea, but implemented as a regular time update on close, what is obviously wrong because it breaks set-in-past functionality (and in general due to the reasons we have LSOM but not SOM) - close always sends *time but does not bother accurately re-gather them from servers, while the local cache could be already stale. in other words this will not work:
      1. client1 open
      2. client2 set-in-past
      3. client1 close

      the reproducer is attached:

      — set-in-past on opened file
      File: '/mnt/lustre/f26c.sanityn'
      Modify: 2020-03-19 22:31:05.000000000 +0300
      File: '/mnt/lustre2/f26c.sanityn'
      Modify: 2020-03-19 22:31:05.000000000 +0300

      — set-in-past on closed file
      File: '/mnt/lustre/f26c.sanityn'
      Modify: 2000-12-31 14:12:59.000000000 +0300
      File: '/mnt/lustre2/f26c.sanityn'
      Modify: 2000-12-31 14:12:59.000000000 +0300

      Attachments

        1. test1.patch
          0.9 kB
          Vitaly Fertman

        Issue Links

          Activity

            People

              vitaly_fertman Vitaly Fertman
              vitaly_fertman Vitaly Fertman
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: