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-14019 Lustre <p>This issue was created by maloo for Vladimir Saveliev &lt;c17830@cray.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/6bf04d76-1386-4340-9901-b90a0ff7e8c5" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/6bf04d76-1386-4340-9901-b90a0ff7e8c5</a></p> <p>test_39l failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>'atime is not updated : 1596474526, should be 1596474527' </pre> </div></div> <p>Other instance:<br/> <a href="https://testing.whamcloud.com/sub_tests/2be49be1-b96d-4b71-96c7-c61a9d74bf7b" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/sub_tests/2be49be1-b96d-4b71-96c7-c61a9d74bf7b</a></p> <p>This is probably related to <a href="https://jira.whamcloud.com/browse/LU-1783" title="sanity test_39l failed: atime is not updated" class="issue-link" data-issue-key="LU-1783">LU-1783</a> and <a href="https://jira.whamcloud.com/browse/LU-4765" title="Failure on test suite sanity test_39l: atime is not updated" class="issue-link" data-issue-key="LU-4765"><del>LU-4765</del></a>, although, test output is somewhat different.</p> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity test_39l - 'atime is not updated : 1596474526, should be 1596474527'</p> LU-14019

sanity test_39l: @@@@@@ FAIL: atime is not updated

Bug Minor Open Unresolved WC Triage Maloo Thu, 8 Oct 2020 15:40:32 +0000 Wed, 15 Nov 2023 12:17:07 +0000 Lustre 2.14.0 0 2 <p>Part of test 39l:<br/>  <br/>         do_facet $SINGLEMDS lctl set_param -n mdd.<b>MDT0000</b>.atime_diff=2<br/>         sleep 3<br/>  <br/>         # test setting directory atime when now &gt; dir atime + atime_diff                                                                                                                                  <br/>         local d1=$(date +%s)<br/>         ls $DIR/$tdir<br/>         local d2=$(date +%s)<br/>         cancel_lru_locks mdc <br/>         atime=$(stat -c %X $DIR/$tdir)<br/>         [ "$atime" -ge "$d1" -a "$atime" -le "$d2" ] ||<br/>                 error "atime is not updated  : $atime, should be $d2”   &lt;=== The message is wrong.  Should be "must meet condition d1 &lt;= atime &lt;= d2"<br/>  <br/> In our test, we see sanity test_39l: @@@@@@ FAIL: atime is not updated  : 1618155458, should be 1618155459 (d2 - atime == 1)<br/>  <br/> That indicates the value of d1 fails to meet the condition "$atime" -ge "$d1" but d1 is not logged unfortunately.<br/>  <br/> Observation: It's inherently unstable to check local time against the timestamps from a distributed file system.  It's quite possible that local time d1 is larger than file's atime, if the clocks are slightly out of sync.  Using atime as an example, we want to test:<br/>  <br/> 1. The atime increments (or stays the same depending on the granularity of the timestamp) with each access.<br/> 2. The atime falls into a reasonable range of the local time (say plus/minor a second).</p> Development Rank 1|i01by7: Rank (Obsolete) 9223372036854775807 Severity