[LU-4939] Need to be able to sanely query and change MGS configuration information

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.0, Lustre 2.10.7
• Labels: llnl patch
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Prakash Surya (Inactive)

Description

Is there a sane way to determine what NIDs a server is configured with as determined by the MGS?

I know there's lctl list_nids, but that's not what I want. I need to determine which NIDs the MGS has for a given server, as I think the MGS is handing a client a non-existent NID for a server.

Issue Links

• is related to: LU-11566 sanity test_60aa: llog_print_cb()) not enough space for print log records
• is related to: LU-11684 conf-sanity test 123: FAIL: jobid_var=procname_uid is not testname
• is related to: LU-12529 How to remove bad config values from MGS logs

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/34250/
Subject: LU-4939 obdclass: llog_print params file
Project: fs/lustre-release
Branch: b2_10
Current Patch Set:
Commit: fb77f09ac8907059552eb5d606e9f8bcab580426

[Gerrit Updater]

Andreas Dilger ([e-mail]) uploaded a new patch: https://review.whamcloud.com/34250
Subject: LU-4939 obdclass: llog_print params file
Project: fs/lustre-release
Branch: b2_10
Current Patch Set: 1
Commit: a0a13a6981bee02af102c00b2cf08717fd2f6bab

[Peter Jones]

Landed for 2.12

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/31846/
Subject: LU-4939 utils: allow configuration through yaml files
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 8961f2d8e263c831ebebc47081d8e8ac61ffbcd9

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/31931/
Subject: LU-4939 tests: fix typo in sanity.sh
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 47db24368d4191df91c80ad9ed60a62fa26922b5

[Gerrit Updater]

Ben Evans ([e-mail]) uploaded a new patch: https://review.whamcloud.com/31931
Subject: LU-4939 tests: fix typo in sanity.sh
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 005206fd806c7bbc525ca34151f0442ad4a3f971

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/31620/
Subject: LU-4939 obdclass: llog_print params file
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 320e736191cce766cd0838ebbd5e76f1aefa1a6f

[Gerrit Updater]

Ben Evans ([e-mail]) uploaded a new patch: https://review.whamcloud.com/31846
Subject: LU-4939 utils: allow configuration through yaml files
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 27084dd994954bc3a9c9a139c67a071bb786c0ce

[Gerrit Updater]

Ben Evans ([e-mail]) uploaded a new patch: https://review.whamcloud.com/31620
Subject: LU-4939 obdclass: llog_print params file
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: c2c410974cec3bcf1665b2c9bf9a85679e1e3a65

[Andreas Dilger]

For whatever reason, I don't recall ever seeing this ticket, nor the patch that was pushed against it.

There was a command added many years ago "lctl --device %MGS llog_print \$<llog_name>" that will dump the current config llog (e.g. testfs-client or testfs-OST0001) from a running MGS.  In 2.6 this was changed to dump the llog in YAML format, for ease of reading/parsing (the pre-2.6 format was a huge mess and mostly unusable) via patch http://review.whamcloud.com/4254 "LU-2149 llog: lctl to work with llogs from command line".  In 2.10 the llog_print command was simplified to allow "lctl --device MGS llog_print <llog_name>" (i.e. without '%' before the device name, and without '$' before llog_name) via patch https://review.whamcloud.com/25468 "LU-9153 utils: improve llog name parsing".

Ideally, the offline llog_reader tool would be improved to also dump the config llogs in the same YAML format (possibly with a --yaml flag to keep compatibility with the old format, if that is considered important).

What is really needed at this point is to be able to take the YAML data as input and apply the tuning parameters to a system after a --writeconf or if the filesystem was reformatted.