[LU-60] mkfs.lustre's --mgsnode=nid:nid syntax not working

• Type: Bug
• Resolution: Incomplete
• Priority: Minor
• Affects Version/s: Lustre 2.1.0, Lustre 1.8.6
• Severity: 3
• Assignee: WC Triage
• Reporter: Brian Murrell (Inactive)

Description

Given the following node mapping:

192.168.122.147	oss1
192.168.122.160	oss2
192.168.122.89	mds1
192.168.122.115	mds2

When I format an OST with the following syntax:

oss1# mkfs.lustre --ost --reformat --mgsnode=mds1:mds2 --failnode=oss2 /dev/vda

and then try to mount it, the mount fails with dmesg reporting:

Lustre: 2876:0:(client.c:1476:ptlrpc_expire_one_request()) @@@ Request x1359778535178425 sent from MGC192.168.122.89@tcp to NID 192.168.122.115@tcp 5s ago has timed out (5s prior to deadline).
  req@ffff8100174bcc00 x1359778535178425/t0 o250->MGS@MGC192.168.122.89@tcp_0:26/25 lens 368/584 e 0 to 1 dl 1296831448 ref 1 fl Rpc:N/0/0 rc 0/0
LustreError: 6413:0:(obd_mount.c:1097:server_start_targets()) Required registration failed for lustre-OSTffff: -4
LustreError: 6413:0:(obd_mount.c:1655:server_fill_super()) Unable to start targets: -4
LustreError: 6413:0:(obd_mount.c:1438:server_put_super()) no obd lustre-OSTffff
LustreError: 6413:0:(obd_mount.c:147:server_deregister_mount()) lustre-OSTffff not registered

However if I format with the following syntax:

oss1# mkfs.lustre --ost --reformat --mgsnode=mds1 --mgsnode=mds2 --failnode=oss2 /dev/vda

mounting succeeds.

Just for good measure I tried a , instead of a : between the NIDs and the result is the same as for the :.

Issue Links

• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA