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-9267 Lustre <p>This issue was created by maloo for nasf &lt;fan.yong@intel.com&gt;</p> <p>Please provide additional information about the failure here.</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/5fb16200-139f-11e7-8920-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/5fb16200-139f-11e7-8920-5254006e85c2</a>.</p> <p>The test logs show that:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>02:13:05:onyx-31vm3: cannot import 'lustre-mdt2': more than one matching pool 02:13:05:onyx-31vm3: import by numeric ID instead 02:13:41:Tests running for 75 minutes, 0 restarts, current suite:test lustre-initialization-1:lustre-initialization_1 </pre> </div></div> LU-9267

lustre-initialization-1 failed: Test system failed to start single suite, so abandoning all hope and giving up

Bug Minor Open Unresolved WC Triage Maloo Tue, 28 Mar 2017 10:32:52 +0000 Fri, 23 Mar 2018 14:20:33 +0000 0 4 <p>Fan Yong, are you sure this isn't caused by the snapshot patches? Having multiple pools with the same name definitely seems like a snapshot problem. </p> <p>I have the same problem at home (with ldiskfs) when I make a <tt>dd</tt> copy of the MDT to a backup device, and I try to mount the disk by label, if I don't change the label on the MDT backup.</p> <p>Lustre snapshot needs to be triggered manually. In the lustre-initialization-1, nobody triggers Lustre snapshot, and there is node-provisioning-1 just before the lustre-initialization-1, the system should be clean when lustre-initialization-1. So I do not think it is related with the patch.</p> <p>is this still an issue?</p> Related LU-10828 Development Rank 1|hzz8gf: Rank (Obsolete) 9223372036854775807 Severity