[LU-2431] llmount.sh fails with FSTYPE=zfs

• Status: Closed
• Project: Lustre
• Affects Version/s: Lustre 2.4.0
• Type: Bug
• Priority: Minor
• Reporter: John Hammond
• Assignee: WC Triage
• Resolution: Duplicate
• Labels: tests
• Severity: 3

Description

After 682f3e19 running llmount.sh with FSTYPE=zfs fails while trying to create the MGS:

# FSTYPE=zfs ./lustre/tests/llmount.sh 
Stopping clients: r63-lm /mnt/lustre (opts:)
Stopping clients: r63-lm /mnt/lustre2 (opts:)
Loading modules from /usr/src/lustre-release/lustre/tests/..
detected 4 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 mgs: lustre-mgs/mgs

mkfs.lustre FATAL: Unable to create filesystem lustre-mgs/mgs (256)

mkfs.lustre FATAL: mkfs failed 256

Is this a "supported" usage of llmount.sh? If not then whet is the recommended way of setting up a small zfs instance for test purposes?

I got it back to the combined MDT/MGS case by default using the following patch. But there would still seem to be some issues with the non-combined case.

diff --git a/lustre/tests/test-framework.sh b/lustre/tests/test-framework.sh
index 921063e..1ac1085 100644
--- a/lustre/tests/test-framework.sh
+++ b/lustre/tests/test-framework.sh
@@ -2676,7 +2676,7 @@ mgsdevname() {
                        eval DEVPTR=${!DEVNAME:=${MDSDEV1}};;
                zfs )
                        #dataset name is independent of vdev device names
-                       eval DEVPTR=${FSNAME}-mgs/mgs;;
+                       eval DEVPTR=${!DEVNAME:=${MDSDEV1}};;
                * )
                        error "unknown fstype!";;
        esac

Comments

[Jodi Levi (Inactive)]

Duplicate of LU-1187 and Change, 4774