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-14930 Lustre <p>Several reports point to the problem with INACTIVE recovery_status on MDT and OSTs. Such status is reported when server has no clients in <tt>last_rcvd</tt> file to recover, but in reported cases there were clients for sure and servers were under load. </p> LU-14930

Server has no clients to recover after failover

Bug Major Resolved Fixed Mikhail Pershin Mikhail Pershin Wed, 11 Aug 2021 17:50:52 +0000 Mon, 22 Aug 2022 14:57:12 +0000 Wed, 25 Aug 2021 20:20:41 +0000 Lustre 2.15.0 0 5 <p>"Mike Pershin &lt;mpershin@whamcloud.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/44610" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/44610</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14930" title="Server has no clients to recover after failover" class="issue-link" data-issue-key="LU-14930"><del>LU-14930</del></a> mdt: abort_recov_mdt shouldn't abort client recovery<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 905a73042510887855ae709d2a04c0b001bd2333</p> <p>I am not sure that this is the real reason for the issue, but found that while investigation and think that might be related. At least that could explain why server has no more clients on storage</p> <p>Hello,</p> <p>I have observed that "umount -f &lt;target&gt;" removes clients from last_rcvd.<br/> So at the next "mount" status INACTIVE is displayed (recovery is disabled and errors will be reported on user applications).</p> <p>Not sure if is related but it could be good to know.</p> <p>yes, that is exactly the reason for INACTIVE <tt>recovery_status</tt>, because it means not that target is 'inactive' but that recovery is 'inactive' which can be in two cases - it is yet not started, i.e. server didn't read client data from storage OR it was not started at all because server has no clients in <tt>last_rcvd.</tt><br/> In reports mentioned in description servers were unmounted with '-f' option so that explains what we have seen. That also means patch is not quite related though it still fixes existing problem</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/44610/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/44610/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14930" title="Server has no clients to recover after failover" class="issue-link" data-issue-key="LU-14930"><del>LU-14930</del></a> mdt: abort_recov_mdt shouldn't abort client recovery<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 6fd75f264c5f5c186bbfe559e1a98fb3769d8128</p> <p>Landed for 2.15</p> <p>"Gian-Carlo DeFazio &lt;defazio1@llnl.gov&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/45245" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/45245</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14930" title="Server has no clients to recover after failover" class="issue-link" data-issue-key="LU-14930"><del>LU-14930</del></a> mdt: abort_recov_mdt shouldn't abort client recovery<br/> Project: fs/lustre-release<br/> Branch: b2_14<br/> Current Patch Set: 1<br/> Commit: b4f396a1efe57029160d13e2419d8730925f3438</p> <p>"Etienne AUJAMES &lt;eaujames@ddn.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/48285" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/48285</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14930" title="Server has no clients to recover after failover" class="issue-link" data-issue-key="LU-14930"><del>LU-14930</del></a> mdt: abort_recov_mdt shouldn't abort client recovery<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: 1<br/> Commit: f69cc05fca93db87d5c69cfe6b86aae0fe1ce6a2</p> Related LU-12546 Development Rank 1|i021iv: Rank (Obsolete) 9223372036854775807 Severity