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-2471 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/70b27b00-4295-11e2-8dba-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/70b27b00-4295-11e2-8dba-52540035b04c</a>.</p> <p>The sub-test test_24a failed with the following error:</p> <blockquote> <p>test_24a returned 10</p></blockquote> <p>CMD: client-29vm3 mkfs.lustre --mgsnode=client-29vm3@tcp --fsname=lustre --mdt --index=0 --param=sys.timeout=20 --param=lov.stripesize=1048576 --param=lov.stripecount=0 --param=mdt.identity_upcall=/usr/sbin/l_getidentity --backfstype=ldiskfs --device-size=2097152 --mkfsoptions=\"-E lazy_itable_init\" --mountfsoptions=errors=remount-ro,iopen_nopriv,user_xattr,acl --nomgs --mgsnode=client-29vm3@tcp --fsname=test1234 --reformat lustre-mdt1_2/mdt1_2 /dev/lvm-MDS/S1<br/> client-29vm3: mkfs.lustre: failed to resolve path to lustre-mdt1_2/mdt1_2<br/> client-29vm3: <br/> client-29vm3: mkfs.lustre FATAL: unable to prepare backend (2)<br/> client-29vm3: mkfs.lustre: exiting with 2 (No such file or directory)</p> lustre master build #1104 with ZFS LU-2471

conf-sanity test_24a: mkfs.lustre FATAL: unable to prepare backend

Bug Blocker Closed Fixed Li Wei Maloo HB Tue, 11 Dec 2012 17:21:10 +0000 Tue, 27 Aug 2019 00:01:10 +0000 Sat, 22 Dec 2012 01:00:18 +0000 Lustre 2.4.0 Lustre 2.4.0 0 2 <p>The format command Sarah quoted is indeed inconsistent:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>... --backfstype=ldiskfs ... lustre-mdt1_2/mdt1_2 /dev/lvm-MDS/S1 </pre> </div></div> <p>According the "lustre-initialisation" log in the Maloo session, Autotest gave these:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>06:51:51:export MDSFSTYPE=ldiskfs 06:51:51:export MGSFSTYPE=zfs ... 06:51:51:export OSTFSTYPE=zfs 06:51:52:export FSTYPE=zfs </pre> </div></div> <p>Thus, "--backfstype=ldiskfs" was correct, while mdsdevname() and mdsvdevname() generated incorrect device names. There are two issues need to be fixed here:</p> <ol> <li>Autotest should set MDSFSTYPE to "zfs". Typo?</li> <li>facet_type() should recognise inputs like "mds1_2".</li> </ol> <p>I'll submit patch for issue 2.</p> <p><a href="http://review.whamcloud.com/4849" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4849</a></p> <p>The patch has landed to master. The Autotest issue has been reported to Chris and, I believe, has been fixed in Autotest configurations.</p> Related LU-9043 Development Rank 1|hzvdnb: Rank (Obsolete) 5817 Severity