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

metadata-updates: FAIL: wrong timestamps

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • Lustre 2.9.0
    • Lustre 2.9.0
    • None
    • 3
    • 9223372036854775807

    Description

      metadata-updates test failed as follows:

      onyx-40vm2: /mnt/lustre/d0.metadata-updates/onyx-40vm1/testfile [ atime mtime ] expected : 978307200 1115251200 ;  got : 1469410011 1115251200 
      onyx-40vm1: /mnt/lustre/d0.metadata-updates/onyx-40vm2/testfile [ atime mtime ] expected : 978307200 1115251200 ;  got : 1469410011 1115251200 
       metadata-updates : @@@@@@ FAIL: wrong timestamps
      

      Maloo reports:
      https://testing.hpdd.intel.com/test_sets/825136bc-524f-11e6-bf87-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/957409a0-5037-11e6-bf87-5254006e85c2
      https://testing.hpdd.intel.com/test_sets/92afe362-5008-11e6-9f8e-5254006e85c2

      Attachments

        Issue Links

          Activity

            [LU-8446] metadata-updates: FAIL: wrong timestamps
            standan Saurabh Tandan (Inactive) made changes -
            Remote Link New: This issue links to "Page (HPDD Community Wiki)" [ 18922 ]
            pjones Peter Jones made changes -
            Link Original: This issue is related to LDEV-95 [ LDEV-95 ]
            pjones Peter Jones made changes -
            Link New: This issue is duplicated by LDEV-95 [ LDEV-95 ]
            pjones Peter Jones made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            pjones Peter Jones added a comment -

            Landed for 2.9

            pjones Peter Jones added a comment - Landed for 2.9

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/22623/
            Subject: LU-8446 llite: clear inode timestamps after losing UPDATE lock
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 4a5e3556a6016cf5ded9c4126454916ab847a1b6

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/22623/ Subject: LU-8446 llite: clear inode timestamps after losing UPDATE lock Project: fs/lustre-release Branch: master Current Patch Set: Commit: 4a5e3556a6016cf5ded9c4126454916ab847a1b6

            Niu Yawei (yawei.niu@intel.com) uploaded a new patch: http://review.whamcloud.com/22623
            Subject: LU-8446 llite: clear inode timestamps after losing UPDATE lock
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: c631f414ea2d3e9d3acbb653bc85c10f68dcb9d5

            gerrit Gerrit Updater added a comment - Niu Yawei (yawei.niu@intel.com) uploaded a new patch: http://review.whamcloud.com/22623 Subject: LU-8446 llite: clear inode timestamps after losing UPDATE lock Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: c631f414ea2d3e9d3acbb653bc85c10f68dcb9d5

            Thanks for the log, Yujian.

            The log looks normal: OST updated lvb correctly, and clients even returned correct timestamps on glimplse shortly before the failure point. I'll investigate it futher.

            niu Niu Yawei (Inactive) added a comment - Thanks for the log, Yujian. The log looks normal: OST updated lvb correctly, and clients even returned correct timestamps on glimplse shortly before the failure point. I'll investigate it futher.
            yujian Jian Yu made changes -
            Attachment New: metadata-updates.1472950648.tar.gz [ 23053 ]
            jamesanunez James Nunez (Inactive) made changes -
            Link New: This issue is related to LU-8603 [ LU-8603 ]

            People

              niu Niu Yawei (Inactive)
              yujian Jian Yu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: