[LU-13722] LNet lnetctl discrepancy in YAML output Created: 27/Jun/20 Updated: 12/May/21 Resolved: 12/May/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.15.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Cyril Bordage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | easy, lnet | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
global show:
global:
numa_range: 0
max_intf: 200
discovery: 1
drop_asym_route: 0
retry_count: 2
transaction_timeout: 50
health_sensitivity: 100
recovery_interval: 1
router_sensitivity: 100
lnd_timeout: 16
But when setting max_intf we need to use: lnetctl set max_interfaces <value> the literal max_interfaces should be used for both the show and set |
| Comments |
| Comment by Gerrit Updater [ 16/Oct/20 ] |
|
Cyril Bordage (cbordage@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/40269 |
| Comment by Bruno Travouillon (Inactive) [ 21/Oct/20 ] |
|
I guess it will change the output of lnetctl export. If so, lnetctl import should support both `max_intf` and `max_interfaces`? |
| Comment by Cyril Bordage [ 21/Oct/20 ] |
|
Yes, you are totally right. Will fix that. |
| Comment by Gerrit Updater [ 11/May/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/40269/ |
| Comment by Peter Jones [ 12/May/21 ] |
|
Landed for 2.15 |