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-2593 Lustre <p>After a cluster was bounced during a partner's Chroma evaluation, the filesystem came back up in recovery. The site admin did not realize that they should attempt to re-mount their client in order to move forward, and therefore the MDT was blocked on tgt_recov for over 12 hours.</p> <p>Ultimately, the site admin was instructed to use lctl abort_recov on the MDT device to move forward, and advised that in the future their client(s) should remount the filesystem instead of using lctl.</p> <p>As part of the investigation into what was happening, it was observed that dmesg on the MDS was full of repeating messages about tgt_recov (log excerpt attached). At adilger's request, I created this ticket to track a request to quiet these repeating messages down in order to reduce the chance that important messages might be lost in the spam.</p> Lustre 2.1.3 LU-2593

Quiet log spam while waiting for initial client connect in recovery

Improvement Blocker Closed Not a Bug Mikhail Pershin Michael MacDonald LB Wed, 9 Jan 2013 13:14:33 +0000 Mon, 11 Feb 2013 04:58:24 +0000 Mon, 11 Feb 2013 04:58:12 +0000 0 3 <p>as far as I can see this is kernel message but not Lustre one, also there is message about how to shut it down:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">Jan 7 15:28:58 chroma-mds0 kernel: INFO: task tgt_recov:6363 blocked <span class="code-keyword">for</span> more than 120 seconds. Jan 7 15:28:58 chroma-mds0 kernel: "echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs" disables <span class="code-keyword">this</span> message. </pre> </div></div> <p>I don't know what can we do here except following that advice.</p> <p>not Lustre bug</p> Development Rank 1|hzvetr: Rank (Obsolete) 6043