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-2787 Lustre <p>This is reported in every single patch review. </p> <p>I didn't find an LU of this common error so I filed one. It seems very serious.</p> <p>Perhaps this is a TT issue I don't know. I took a quick look at the system logs and all I saw were systems just sitting around for some time. </p> <p>Actual error logs can be seen here:<br/> <a href="https://maloo.whamcloud.com/test_sets/216df032-71f8-11e2-aad1-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/216df032-71f8-11e2-aad1-52540035b04c</a></p> <p>The tests reports:<br/> Failure Rate: 44.00% of last 100 executions <span class="error">&#91;all branches&#93;</span> </p> a patch pushed via git. LU-2787

review-zfs lustre-initialization_1 It is broken.

Bug Major Resolved Duplicate WC Triage Keith Mannthey Fri, 8 Feb 2013 15:11:25 +0000 Tue, 20 Aug 2013 16:35:14 +0000 Fri, 8 Feb 2013 20:30:28 +0000 0 3 <p>Keith,<br/> you are right that this is a fairly serious problem, which should hopefully be fixed soon. I believe that there are a number of tickets tracking ZFS problems already, and Nathaniel and Li Wei are working to get ZFS running again. Unfortunately, since we weren't doing ZFS testing all the time, a number of bugs were introduced that now need to be fixed.</p> <p>In order to make this a useful bug report, you need to look into the maloo test logs to see what the root of the problem is. Normally the "autotest" log is interesting for lustre-initialization-1 failures. In this case it shows near the end:</p> <p><a href="https://maloo.whamcloud.com/test_logs/2401a938-71f8-11e2-aad1-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_logs/2401a938-71f8-11e2-aad1-52540035b04c</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Invalid filesystem name /dev/lvm-MDS/P1 </pre> </div></div> <p>which is <a href="https://jira.whamcloud.com/browse/LU-2469" title="Test-framework.sh ignores MDSDEV when FSTYPE=zfs" class="issue-link" data-issue-key="LU-2469"><del>LU-2469</del></a> and there is a patch at <a href="http://review.whamcloud.com/5016" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5016</a>.</p> <p>Thanks for the pointers to the autotest log. I had looked at system, dmesg, and console logs. lustre-initialization-1 falls into TT issue for the most part for me, I will be more through in the future. In general I only looked at the ZFS logs because you have to dig into the maloo logs to even find out it was the ZFS run (there is an open TT for this issue.) </p> <p>I was just wanting to be sure there was an LU placeholder for the issue. I searched for open LU's but I didn't seem to find <a href="https://jira.whamcloud.com/browse/LU-2469" title="Test-framework.sh ignores MDSDEV when FSTYPE=zfs" class="issue-link" data-issue-key="LU-2469"><del>LU-2469</del></a>, it is great to see all the hard work stabilizing ZFS in autotest. </p> Duplicate LU-2469 Development Rank 1|hzviwn: Rank (Obsolete) 6753 Severity