[LU-15084] Unsupported parameter mds_attr_cpu_bind error when updating from a 2.12 LTS release to master Created: 12/Oct/21 Updated: 12/Oct/21 Resolved: 12/Oct/21 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Upstream |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Petros Koutoupis | Assignee: | WC Triage |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Epic/Theme: | upstream | ||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
When updating from 2.12 (LTS) to latest master, I get the following unsupported parameter error: [ 495.249412] mdt: Unknown parameter `mds_attr_cpu_bind' [ 495.262504] LustreError: 158-c: Can't load module 'mdt' Are parameters such as these supported from one LTS to the next (i.e. 2.15)? |
| Comments |
| Comment by Andreas Dilger [ 12/Oct/21 ] |
|
This attribute has done nothing since Lustre 2.1, according to my Typically I'm on the side of maintaining compatibility, but this is totally safe to remove from the 2.12 LTS system before the upgrade without any loss of functionality, so I'm not sure what benefit there would be to keeping compatibility? |
| Comment by Petros Koutoupis [ 12/Oct/21 ] |
|
@Andreas Dilger, I spoke with my team and they provided me with the history on why it was part of our configuration and why it may not have been immediately removed. Thank you for your input. I will close this issue. |