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-5102 Lustre <p>run sh llmount with current master I got this</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@mds tests]# sh llmount.sh Stopping clients: mds /mnt/lustre (opts:) Stopping clients: mds /mnt/lustre2 (opts:) Loading modules from /work/lustre-release/lustre/tests/.. detected 2 online CPUs by sysfs Force libcfs to create 2 CPU partitions ../libcfs/libcfs/libcfs options: 'cpu_npartitions=2' debug=vfstrace rpctrace dlmtrace neterror ha config ioctl super subsystem_debug=all -lnet -lnd -pinger gss/krb5 is not supported quota/lquota options: 'hash_lqs_cur_bits=3' Formatting mgs, mds, osts Format mds1: /tmp/lustre-mdt1 mkfs.lustre FATAL: unhandled fs type 1 'ldiskfs' mkfs.lustre FATAL: unable to prepare backend (22) mkfs.lustre: exiting with 22 (Invalid argument) </pre> </div></div> <p>It seems commit "<a href="https://jira.whamcloud.com/browse/LU-4606" title="Lustre hard codes libzfs.so.1 in lustre/utils/mount_utils_zfs.c" class="issue-link" data-issue-key="LU-4606"><del>LU-4606</del></a> utils: Mount uses so for backing fstype" insist to load plugin for a given mount_type from <tt>$pkglibdir/mount_osd_$FSTYPE.so</tt>, which will bring problem for local testing environment.</p> LU-5102

Loading plugin for a given mount_type from ${pkglibdir}/mount_osd_FSTYPE.so" brings problem to local testing.

Bug Critical Resolved Fixed Nathaniel Clark Di Wang Mon, 26 May 2014 17:40:32 +0000 Thu, 5 Jun 2014 13:10:38 +0000 Thu, 5 Jun 2014 13:10:38 +0000 Lustre 2.6.0 Lustre 2.6.0 0 5 <p>I think there are a few ways this could be solved:</p> <ul class="alternate" type="square"> <li>have mount_lustre.c check for $LUSTRE in the environment and use that as the path prefix for <tt>mount_ost_$FSTYPE.so</tt></li> <li>have mount_lustre.c check the pathname under which it is executed, and if a relative or absolute path is used (i.e. with '/' in it) then use the basename to look for <tt>mount_ost_$FSTYPE.so</tt></li> <li>add an argument to mount_lustre.c to specify the path for libraries</li> </ul> <p>Or add $PWD/./lustre/utils/.libs/ to LD_LIBRARY_PATH and pass "mount_ost_$FSTYPE.so" to dlopen(). Or some combination of that and Andreas's suggestions.</p> <p>looks for $LUSTRE after looking in libdir<br/> <a href="http://review.whamcloud.com/10468" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10468</a></p> <p>Looking at invocation path doesn't work because of mount.lustre always needing to be invoked from /sbin by mount.</p> <p>Patch landed to Master.</p> Related LU-4606 Development Rank 1|hzwn33: Rank (Obsolete) 14082 Severity