https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-8446 Lustre <p>metadata-updates test failed as follows:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>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 </pre> </div></div> <p>Maloo reports:<br/> <a href="https://testing.hpdd.intel.com/test_sets/825136bc-524f-11e6-bf87-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/825136bc-524f-11e6-bf87-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/957409a0-5037-11e6-bf87-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/957409a0-5037-11e6-bf87-5254006e85c2</a><br/> <a href="https://testing.hpdd.intel.com/test_sets/92afe362-5008-11e6-9f8e-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/92afe362-5008-11e6-9f8e-5254006e85c2</a></p> LU-8446

metadata-updates: FAIL: wrong timestamps

Bug Critical Resolved Fixed Niu Yawei Jian Yu Wed, 27 Jul 2016 18:42:54 +0000 Tue, 1 Nov 2016 18:17:03 +0000 Thu, 29 Sep 2016 17:47:14 +0000 Lustre 2.9.0 Lustre 2.9.0 0 6 <p>Hi Jian,</p> <p>Can you determine what build this problem starting occurring at? That will help to narrow in on potential patches that could have introduced this issue.</p> <p>thanks.<br/> Joe</p> <p>Hi Joe,</p> <p>By searching on Maloo, I found the failure started occurring on 2016-06-06:<br/> <a href="https://testing.hpdd.intel.com/test_sets/12cab8e0-2c5c-11e6-a0ce-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/12cab8e0-2c5c-11e6-a0ce-5254006e85c2</a></p> <p>The build is <a href="https://build.hpdd.intel.com/job/lustre-master/3384" class="external-link" target="_blank" rel="nofollow noopener">https://build.hpdd.intel.com/job/lustre-master/3384</a>. However, it's been removed from Jenkins.</p> <p>Roughly this issue has occurred around 100 times in past 30 days overall.</p> <p>This issue was first seen on 2016-06-06 for build# 3384 on master Tag 2.8.53 which was the last build for this tag:<br/> <a href="https://testing.hpdd.intel.com/test_sets/12cab8e0-2c5c-11e6-a0ce-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/12cab8e0-2c5c-11e6-a0ce-5254006e85c2</a></p> <p>Niu</p> <p>Could you please assist with this issue?</p> <p>Thanks</p> <p>Peter</p> <blockquote><p>I'm not sure why maloo doesn't provide debug log for such kind of test (metadata-updates).</p></blockquote> <p>I think this is because the tests in metadata-updates.sh are not wrapped as test_x() sub-tests. While gathering logs, there are no sub-test names in the log files, and then Maloo doesn't import them (<a href="https://jira.whamcloud.com/browse/LU-8603" title="improve metadata-updates.sh with sub-tests" class="issue-link" data-issue-key="LU-8603"><del>LU-8603</del></a>).</p> <p>From report <a href="https://testing.hpdd.intel.com/test_sets/12cab8e0-2c5c-11e6-a0ce-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/12cab8e0-2c5c-11e6-a0ce-5254006e85c2</a>, we can see:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Dumping lctl log to /logdir/test_logs/2016-06-05/lustre-master-el6_7-x86_64-vs-lustre-master-el7-x86_64--full--2_17_1__3384__-69908717151380-111335/metadata-updates..*.1465232271.log CMD: onyx-32vm3,onyx-32vm4,onyx-32vm5.onyx.hpdd.intel.com,onyx-32vm6 /usr/sbin/lctl dk &gt; /logdir/test_logs/2016-06-05/lustre-master-el6_7-x86_64-vs-lustre-master-el7-x86_64--full--2_17_1__3384__-69908717151380-111335/metadata-updates..debug_log.\$(hostname -s).1465232271.log; dmesg &gt; /logdir/test_logs/2016-06-05/lustre-master-el6_7-x86_64-vs-lustre-master-el7-x86_64--full--2_17_1__3384__-69908717151380-111335/metadata-updates..dmesg.\$(hostname -s).1465232271.log </pre> </div></div> <p>I'm not sure whether autotest has deleted those logs or not. If not, you can find them in /home/autotest/logdir/... or /home/autotest2/logdir/... on the test cluster.</p> <p>Thanks for the log, Yujian.</p> <p>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.</p> <p>Niu Yawei (yawei.niu@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/22623" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/22623</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8446" title="metadata-updates: FAIL: wrong timestamps" class="issue-link" data-issue-key="LU-8446"><del>LU-8446</del></a> llite: clear inode timestamps after losing UPDATE lock<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: c631f414ea2d3e9d3acbb653bc85c10f68dcb9d5</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/22623/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/22623/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8446" title="metadata-updates: FAIL: wrong timestamps" class="issue-link" data-issue-key="LU-8446"><del>LU-8446</del></a> llite: clear inode timestamps after losing UPDATE lock<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 4a5e3556a6016cf5ded9c4126454916ab847a1b6</p> <p>Landed for 2.9</p> Duplicate Related LU-8603 Development Rank 1|hzyiun: Rank (Obsolete) 9223372036854775807 Severity