[LU-7566] mounting lustre emits bogus parse_nidrange() errors to the console

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 2.8.0
• Severity: 3
• Assignee: Jian Yu
• Reporter: John Hammond

Description

u:lustre-release# git describe
2.7.64-31-gacc918d
u:lustre-release# ./lustre/tests/llmount.sh
...

LNet: HW CPU cores: 4, npartitions: 2
...
LDISKFS-fs (loop0): mounted filesystem with ordered data mode. quota=on. Opts: 
LNet: 17713:0:(nidstrings.c:271:parse_nidrange()) can't parse nidrange: "param=lov.stripesize=1048576"
LDISKFS-fs (loop0): mounted filesystem with ordered data mode. quota=on. Opts: 
Lustre: MGS: Connection restored to MGC192.168.122.108@tcp_0 (at 0@lo)
Lustre: Setting parameter lustre-MDT0000-mdtlov.lov.stripesize in log lustre-MDT0000
Lustre: ctl-lustre-MDT0000: No data found on store. Initialize space
Lustre: lustre-MDT0000: new disk, initializing
Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000200000400-0x0000000240000400]:0:mdt
LDISKFS-fs (loop1): mounted filesystem with ordered data mode. quota=on. Opts: 
LNet: 17907:0:(nidstrings.c:271:parse_nidrange()) can't parse nidrange: "param=sys.timeout=20"
LNet: 17907:0:(nidstrings.c:271:parse_nidrange()) Skipped 3 previous similar messages
...

These happen on subsequent mounts as well.

Issue Links

• is related to: LU-7647 Remove annoying message in parse_nidrange() caused by TBF
• is related to: LU-5690 Unable to parse the mdt.nosquash_nids parameter when using commas in expr_list