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-5799 Lustre <p>Running 2.5.3, we see the following message on the console pretty much every time we start an OST:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: lcy-OST000f: deleting orphan objects from 0x0:99109478 to 0x0:99113686 </pre> </div></div> <p>This cleanup is entirely normal. I don't think there is a good reason to be spamming the console with completely normal, expected behavior.</p> <p>Granted, we recently used that message to identify a problem by the <em>absence</em> of that message. But it would be much better to print an error message when lustre skips orphan cleanup because the ranges are unexpectedly bad, and stay silent during normal cleanup.</p> LU-5799

Unhelpful "deleting orphan objects" console message

Bug Minor Resolved Low Priority Bob Glossman Christopher Morrone llnl Thu, 23 Oct 2014 21:30:19 +0000 Wed, 13 Oct 2021 03:02:20 +0000 Wed, 13 Oct 2021 03:02:20 +0000 0 4 <p>Bob is looking into this one</p> <p>in master:<br/> <a href="http://review.whamcloud.com/12407" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12407</a></p> <p>in b2_5:<br/> <a href="http://review.whamcloud.com/12408" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12408</a></p> <p>The recent problem that I alluded to was <a href="https://jira.whamcloud.com/browse/LU-5648" title="corrupt files contain extra data" class="issue-link" data-issue-key="LU-5648"><del>LU-5648</del></a>, as Ned clarified. And as Ned reviewed in gerrit, we will need to add proper debugging messages, not just remove the "deleting orphan objects" message.</p> <p>Bob, it is better to submit patches to master first, and then they can be cherry-picked to b2_5 as needed and add the <tt>Lustre-change:</tt> and <tt>Lustre-commit:</tt> tags at that time. That improves tracking of patches between branches and avoids testing/inspecting the patches twice.</p> <p>I'd actually prefer that these messages be kept, since they provide useful information for debugging (e.g. <a href="https://jira.whamcloud.com/browse/LU-5785" title="recovery-mds-scale test_failover_ost: test_failover_ost returned 1" class="issue-link" data-issue-key="LU-5785"><del>LU-5785</del></a>) in case of recovery problems.</p> <p>I think that we were one of the prime users of those message for a recent bug. But the reason we needed them is that there were no error messages printed in the error path. Instead we needed to intuit an error from the lack of the regular spam message.</p> <p>It seems clear to me that the message is not understandable or usable to an sysadmin. Additionally, it prints out every time which only serves to each sysadmins not to look at lustre messages at all.</p> <p>And if we can agree on that nature of the message, then it does not belong on the console. Instead we should add messages in the error paths.</p> Development End date Mon, 15 Dec 2014 21:30:19 +0000 Rank 1|hzwzdb: Rank (Obsolete) 16264 Severity Start date Thu, 23 Oct 2014 21:30:19 +0000