Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Lustre 2.7.0
-
None
-
3
-
9223372036854775807
Description
When entering a bad nid address in the --servicenode argument. This caused the MDT to not be able to establish a connection and reports in the log as below.
Note the 0@<0:0> at the end that, I am guessing, should be the servicenode failover args and is reporting "0:0" instead. If it had reported the correct args, this would have been a much easier problem to figure out.
Also in the mds log:
class_config_llog_handler()) MGC192.168.20.121@o2ib: cfg command failed: rc = -2 cmd=cf003 0:lustrefs-OST0010-osc-MDT0000 1:lustrefs-OST0010_UUID 2:0@<0:0>