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-994 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/c460154a-3e73-11e1-b417-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/c460154a-3e73-11e1-b417-5254004bbbd3</a>.</p> LU-994

1.8<->2.1.54 Test failure on test suite replay-single 62

Bug Blocker Resolved Fixed Zhenyu Xu Maloo Sun, 15 Jan 2012 00:02:43 +0000 Mon, 19 Mar 2012 13:33:23 +0000 Mon, 19 Mar 2012 13:33:23 +0000 Lustre 2.2.0 0 2 <p>Bobi</p> <p>Could you look into this one please?</p> <p>Thanks</p> <p>Peter</p> <p>Just for the record.</p> <p>MDS recoery start at 1326480370.284875, setting recovery windows in 60 seconds.</p> <p>Client replay req x1390912056905666/t304942678018 (LDLM_ENQUEUE) at 1326480370.283516, and its timeout is 62 seconds</p> <p>At 1326480430.284992 MDS closed its recovery window, while the replay req timedout at 1326480432.535461, so the client was evicted and failed the test.</p> <p>The failure due to that the replay req's timeout time is over the MDS recovery window.</p> <p>I cannot reproduce it on my vm machines. </p> <p>Sarah, would you mind checking what timeout values used on server and client, do they accord? Does AT (adaptive timeout) opened on client side?</p> <p>I use default value for both obd_timeout and ldlm_timeout. So I guess they accord? Yes, AT is enabled on client side. TIMEOUT in my config file is also set to 20.</p> <p>dup of <a href="https://jira.whamcloud.com/browse/LU-1036" title="1.8.7&lt;-&gt;2.1.54 Test failure on test suite replay-single (52)" class="issue-link" data-issue-key="LU-1036"><del>LU-1036</del></a></p> <p>Are you sure that this is a duplicate of LU1036? It seems to relate to a different test # (62 rather than 52) and seems to still be occurring in RC1...</p> <p>it looks like a recovery timeout extension issue, and <a href="https://jira.whamcloud.com/browse/LU-1036" title="1.8.7&lt;-&gt;2.1.54 Test failure on test suite replay-single (52)" class="issue-link" data-issue-key="LU-1036"><del>LU-1036</del></a> also involve the same issue. <a href="https://jira.whamcloud.com/browse/LU-889" title="rework extent_recovery_timer()" class="issue-link" data-issue-key="LU-889"><del>LU-889</del></a> reworks the recovery timeout extension logic. </p> <p>Does the rehit in RC1 contains patch of <a href="https://jira.whamcloud.com/browse/LU-889" title="rework extent_recovery_timer()" class="issue-link" data-issue-key="LU-889"><del>LU-889</del></a>?</p> <p>Yes.<a href="http://git.whamcloud.com/?p=fs/lustre-release.git;a=commit;h=8d4b77e5961c06847f9603ebc607118742ea1a51" class="external-link" target="_blank" rel="nofollow noopener">http://git.whamcloud.com/?p=fs/lustre-release.git;a=commit;h=8d4b77e5961c06847f9603ebc607118742ea1a51</a></p> <p>As per Oleg ok to close - this appears because the version of 1.8.x being tested with does not contain this fix</p> Duplicate LU-1036 Development Rank 1|hzvhiv: Rank (Obsolete) 6488 Severity