Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
None
-
9223372036854775807
Description
The HSM control interface only accept a starting/stopping command for once. The further same command would fail. This behavior is unfriendly to scripts since the script has no idea why exactly the second same command fails.
By contrast, setting "disabled" would always success. The different behaviors of "disabled", "enabled" and "shutdown" is inconsistent thus confusing.
# lctl set_param mdt.*.hsm_control=enabled mdt.lustre0-MDT0000.hsm_control=enabled # lctl set_param mdt.*.hsm_control=enabled error: set_param: setting /proc/fs/lustre/mdt/lustre0-MDT0000/hsm_control=enabled: Operation already in progress # lctl set_param mdt.*.hsm_control=disabled mdt.lustre0-MDT0000.hsm_control=disabled # lctl set_param mdt.*.hsm_control=disabled mdt.lustre0-MDT0000.hsm_control=disabled # lctl set_param mdt.*.hsm_control=shutdown mdt.lustre0-MDT0000.hsm_control=shutdown # lctl set_param mdt.*.hsm_control=shutdown error: set_param: setting /proc/fs/lustre/mdt/lustre0-MDT0000/hsm_control=shutdown: Operation already in progress
Returning success on all redundant starting/stopping commands seems better.
Attachments
Issue Links
- is duplicated by
-
LU-11374 setting mdt.*.hsm_control=enabled should succeed when HSM is already enabled
- Resolved