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-2563 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/2b7215e4-551b-11e2-8753-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/2b7215e4-551b-11e2-8753-52540035b04c</a>.</p> <p>The sub-test lustre-initialization_1 failed with the following error:</p> <blockquote> <p>Test system failed to start single suite, so abandoning all hope and giving up</p></blockquote> <p>This error blocks ZFS testing</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>11:26:52:CMD: client-32vm3 mkfs.lustre --mgs --param=sys.timeout=20 --backfstype=zfs --device-size=2097152 --reformat /dev/lvm-MDS/P1 /dev/lvm-MDS/P1 11:26:52:client-32vm3: 11:26:52:client-32vm3: mkfs.lustre FATAL: Invalid filesystem name /dev/lvm-MDS/P1 11:26:52:client-32vm3: 11:26:52:client-32vm3: mkfs.lustre FATAL: unable to prepare backend (22) 11:26:52:client-32vm3: mkfs.lustre: exiting with 22 (Invalid argument) </pre> </div></div> LU-2563

Failure on test suite lustre-initialization-1: Invalid filesystem name

Bug Blocker Resolved Fixed Chris Gearing Maloo HB zfs Thu, 3 Jan 2013 13:34:32 +0000 Thu, 7 Feb 2013 10:30:34 +0000 Thu, 7 Feb 2013 10:30:34 +0000 Lustre 2.4.0 Lustre 2.4.0 0 5 <p>Ah, t-f.sh has been changed for this part.</p> <p>11:26:34:export MGSDEV=/dev/lvm-MDS/P1<br/> 11:26:34:export MDSDEV=/dev/lvm-MDS/P1</p> <p>MGSDEV definition should be removed for combined mds/mgs test in the config of maloon test.</p> <p>The TF change looks suspicious to me... The MGSDEV assignment, although unnecessary, should work.</p> <p>Autotest was actually using a combined-MDT-MGT configuration. I think the combined_mds_mgs() call in formatall() returned false because mgsdevname() printed "/dev/lvm-MDS/P1" while mdsdevname() printed "lustre-mdt1/mdt1". mgsdevname() should print dataset names for ZFS-based MGTs.</p> <p><a href="http://review.whamcloud.com/4950" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4950</a></p> <p>Patch landed to master, closing bug.</p> <p>Li Wei, in the future please submit patches that affect ZFS with:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Test-Parameters: mdtfilesystemtype=zfs ostfilesystemtype=zfs </pre> </div></div> <p>so that we are able to verify that this is working correctly with ZFS.</p> <p>Sure. I thought Autotest would start a ZFS job automatically. On the other hand, ZFS testing was already broken. Landing this fix won't make things any worse.</p> <p>Looks like the patch that was landed is still broken, per messages in the autotest logs:</p> <p><a href="https://maloo.whamcloud.com/test_sets/04d030c6-6734-11e2-95b6-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/04d030c6-6734-11e2-95b6-52540035b04c</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>12:09:44:/usr/lib64/lustre/tests/test-framework.sh: line 2690: [: /dev/lvm-MDS/P1: unary operator expected </pre> </div></div> <p>which corresponds to the modified code:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">99baa1523 2688) zfs ) 99baa1523 2689) <span class="code-keyword">if</span> [ $(facet_host mgs) = $(facet_host mds1) ] &amp;&amp; 99baa1523 2690) ( [ -z <span class="code-quote">"$MGSDEV"</span> ] || [ $MGSDEV = $(mdsvdevname 1) ] ); then 99baa1523 2691) DEVPTR=$(mdsdevname 1) </pre> </div></div> <p>This is causing all ZFS testing to fail.</p> <p>Minor style note - there is no reason to invoke multiple separate "test" ("[") conditions here:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> zfs) <span class="code-keyword">if</span> [[ $(facet_host mgs) = $(facet_host mds1) &amp;&amp; ( -z <span class="code-quote">"$MGSDEV"</span> -p <span class="code-quote">"$MGSDEV"</span> = <span class="code-quote">"$(mdsdevname1)"</span> ) ]]; then </pre> </div></div> <p>I don't think it is because of the patch above. (I had tested it locally with both combined and separate MGT/MDT as well as ldiskfs and ZFS.) Judging from the error message, mdsvdevname() printed an empty string.</p> <p>Chris, it looks the inconsistency in Autotest configuration is back:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>12:09:14:export mgs_HOST=client-30vm7 12:09:14:export mds_HOST=client-30vm7 12:09:14:export MGSDEV=/dev/lvm-MDS/P1 12:09:14:export MDSDEV=/dev/lvm-MDS/P1 [...] 12:09:15:export MDSFSTYPE=ldiskfs 12:09:15:export MGSFSTYPE=zfs </pre> </div></div> <p>The devices and hosts definitions suggest a combined MGT/MDT, but the fstypes contradict each other. Could you please fix that?</p> <p>P.S., unless we intentionally want mixed-fstype configurations, Autotest could only set "FSTYPE=zfs", leaving XXXFSTYPEs undefined.</p> <p>I don't intend to move to FSTYPE, the definitions of the three separately should work.</p> <p>In the first example mds,met,oat filesystemtype are all zfs.</p> <p>In the second example that Li Wei refers to they are incorrect because they are incorrectly specified in the test parameters in the review message.</p> <p>mdtfilesystemtype=zfs ostfilesystemtype=zfs </p> <p>are specified but mdsfilesystemtype=zfs is not.</p> <p>I've added a comment to the review, and resubmitted it with the additional definition.</p> <p>I didn't notice the "Test-Parameters" line in the session reported by Andreas and incorrectly assumed Autotest had all controls on the generated configuration. Sorry about that.</p> <p>As to "mdsfilesystemtype", I'm not sure how it differs from "mdtfilesystemtype". Actually, I asked this on the wiki quite a while ago. It looks like a typo of "mgsfilesystemtype", but your comment makes me think it is not. Could you clarify, please?</p> <p>Li Wei, I agree - the Test-Parameter should be named "mgsfilesystemtype", NOT "mdsfilesystemtype".</p> <p>I would also be happy if there was a shorthand, like "filesystemtype=zfs" so that the verbose (and potentially failure-inducing) separate parameters can be avoided for the time being.</p> <p>That there is unquestionably still a bug somewhere, unrelated to the Test-parameters, because in the following test the FSTYPE is specified correctly, but the MGS still fails during mkfs.lustre:</p> <p><a href="https://maloo.whamcloud.com/test_logs/7762f79c-6bf6-11e2-b2a5-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_logs/7762f79c-6bf6-11e2-b2a5-52540035b04c</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>13:30:38:export MGSDEV=/dev/lvm-MDS/P1 13:30:38:export MDSDEV=/dev/lvm-MDS/P1 13:30:38:export MDSFSTYPE=zfs 13:30:38:export MGSFSTYPE=zfs 13:30:52:CMD: wtm-26vm7 mkfs.lustre --mgs --param=sys.timeout=20 --backfstype=zfs --device-size=2097152 --reformat /dev/lvm-MDS/P1 /dev/lvm-MDS/P1 13:30:52:wtm-26vm7: 13:30:52:wtm-26vm7: mkfs.lustre FATAL: Invalid filesystem name /dev/lvm-MDS/P1 </pre> </div></div> <p>Nothing is on the MDS or client console or debug logs.</p> <p>Emoly's patch is based on a Jan 17 master, which does not include the fix above. It looks like a result of the original issue. I'll ask her to rebase if necessary.</p> <p>Test failure was run without the patch that should fix this. Closing bug again.</p> Development Rank 1|hzveif: Rank (Obsolete) 5992 Severity