table of contents
lsm_volume_write_cache_policy_update(3) | Libstoragemgmt C API Manual | lsm_volume_write_cache_policy_update(3) |
NAME¶
lsm_volume_write_cache_policy_update - Change RAM write cache policy of the specified volume
SYNOPSIS¶
int lsm_volume_write_cache_policy_update (lsm_connect *conn, lsm_volume *volume, uint32_t wcp, lsm_flag flags);
ARGUMENTS¶
- conn
- Valid lsm_connect pointer.
- volume
- A single lsm_volume
- wcp
- uint32_t. Write cache policy. Valid values are: *
LSM_VOLUME_WRITE_CACHE_POLICY_WRITE_BACK
Change to write back mode. * LSM_VOLUME_WRITE_CACHE_POLICY_AUTO
Change to auto mode: use write back mode when battery/capacitor
is healthy, otherwise use write through. * LSM_VOLUME_WRITE_CACHE_POLICY_WRITE_THROUGH
Change to write through mode. - flags
- Reserved for future use, must be LSM_CLIENT_FLAG_RSVD.
VERSION¶
1.3
DESCRIPTION¶
Change the RAM write cache policy on specified volume. If LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_IMPACT_READ is supported(e.g. HPE SmartArray), the changes on write cache policy might also impact read cache policy. If LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_WB_IMPACT_OTHER is supported(e.g. HPE SmartArray), changing write cache policy to write back mode might impact other volumes in the same system.
CAPABILITY¶
LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_AUTO LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_WRITE_BACK LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_WRITE_THROUGH LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_WB_IMPACT_OTHER LSM_CAP_VOLUME_WRITE_CACHE_POLICY_UPDATE_IMPACT_READ
RETURN¶
LSM_ERR_OK on success else error reason
* LSM_ERR_OK
On success.
* LSM_ERR_NOT_FOUND_VOLUME
When volume not found.
* LSM_ERR_INVALID_ARGUMENT
When any argument is NULL or invalid flags.
* LSM_ERR_NO_SUPPORT
Not supported.
lsm_volume_write_cache_policy_update | April 2023 |