[LU-2112] Interop issue

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.4.0
• Environment: Client: 2.2.0-RC2--PRISTINE-2.6.32-220.4.2.el6.x86_64; Server: 2.3.53
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for Chris Gearing <[e-mail]>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/6801f456-1142-11e2-a645-52540035b04c.

The sub-test lustre-initialization_1 failed with the following error:

04:16:41:CMD: client-28vm8 grep -c /mnt/ost6' ' /proc/mounts
04:16:41:CMD: client-28vm8 lsmod | grep lnet > /dev/null && lctl dl | grep ' ST '
04:16:41:CMD: client-28vm8 /usr/sbin/mkfs.lustre --ost --fsname=lustre --param sys.timeout=20 --device-size=2097152 --mgsnode=client-28vm7@tcp --backfstype ldiskfs --reformat /dev/lvm-OSS/P6
04:16:41:client-28vm8: warning: /dev/lvm-OSS/P6: for Lustre 2.4 and later, the target index must be specified with --index
04:16:41:
04:16:41: Permanent disk data:
04:16:41:Target: lustre:OSTffff
04:16:42:Index: unassigned
04:16:42:Lustre FS: lustre
...snip
04:16:43:debug=0x33f0404
04:16:43:subsystem_debug=0xffb7e3ff
04:16:43:gss/krb5 is not supported
04:16:43:Setup mgs, mdt, osts
04:16:43:CMD: client-28vm7 mkdir -p /mnt/mds1
04:16:43:Starting mds1: -o user_xattr,acl /dev/lvm-MDS/P1 /mnt/mds1
04:16:43:CMD: client-28vm7 mkdir -p /mnt/mds1; mount -t lustre -o user_xattr,acl /dev/lvm-MDS/P1 /mnt/mds1
04:16:43:client-28vm7: mount.lustre: /dev/mapper/lvm--MDS-P1 has no index assigned (probably formatted with old mkfs)
04:17:08:Tests running for 37 minutes, 0 restarts, current suite:test lustre-initialization-1:lustre-initialization_1
04:18:08:Tests running for 38 minutes, 0 restarts, current suite:test lustre-initialization-1:lustre-initialization_1
04:19:08:Tests runnin

This issue occurs with 1.8, 2.2 and presumably 2.1 clients. The client test scripts probably need to be updated on 1.8,2.1,2.2 to provide index for later servers

Issue Links

• duplicates: LU-1526 interop 1.8,2.1 -> 2.4 "mkfs.lustre FATAL: The target index must be specified with --index"

Comments

[Andreas Dilger]

The default --index=0 was added for MDTs, along with printing a warning in http://review.whamcloud.com/4293

[Andreas Dilger]

Would it be reasonable to assume index = 0 in the 2.4 code if no index is specified for the MDT? Alternately, or in addition, the warning in mkfs_lustre.c should be upgraded to an error, and should also be back-ported to 2.1 if it isn't already, to give users more warning about this change.