[LU-15106] deprecated obdfilter parameter warn on read Created: 14/Oct/21 Updated: 27/Oct/21 Resolved: 27/Oct/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.14.0, Lustre 2.15.0 |
| Fix Version/s: | Lustre 2.15.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | Andreas Dilger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
There are a number of obdfilter parameter files that report an error even when they are read, which is confusing for the users: # lctl get_param obdfilter.*.* [225584.240206] ofd: 'obdfilter.*.read_cache_enabled' is deprecated, use 'osd-*.read_cache_enabled' instead [225584.240244] ofd: 'obdfilter.*.readcache_max_filesize' is deprecated, use 'osd-*.readcache_max_filesize' instead [225584.240446] ofd: 'obdfilter.*.sync_on_lock_cancel' is deprecated, use 'obdfilter.*.sync_lock_cancel' instead [225584.240652] ofd: 'obdfilter.*.writethrough_cache_enabled' is deprecated, use 'osd-*.writethrough_cache_enabled' instead It should only print an error if the parameters are actually written. Several of these parameters are slated for removal in 2.15, but since the deprecation warning was only added in 2.12.53 and not backported, and there has not been an LTS release since then, it would be better to bump the removal to 2.16 so at least the 2.15 LTS release includes the warning message. |
| Comments |
| Comment by Gerrit Updater [ 14/Oct/21 ] |
|
"Andreas Dilger <adilger@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45246 |
| Comment by Gerrit Updater [ 27/Oct/21 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45246/ |
| Comment by Peter Jones [ 27/Oct/21 ] |
|
Landed for 2.15 |