lsm_volum...che_update(3)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

✨ lsm_volume_physical_disk_cache_update ✨

okay bestie, gather round, because we're diving into the Libstoragemgmt C API Manual and honestly? this one's a little cutie. it's called lsm_volume_physical_disk_cache_update, and it does exactly one thing but it does it so well. πŸ’…


🌸 NAME 🌸

lsm_volume_physical_disk_cache_update β€” change the RAM physical disk cache setting of a specified volume. that's it. that's the whole job. main character energy fr fr. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int lsm_volume_physical_disk_cache_update (lsm_connect *conn, lsm_volume
*volume, uint32_t pdc, lsm_flag flags);

πŸ’– ARGUMENTS πŸ’–

  • conn β€” a valid lsm_connect pointer. she has to be real, no fake ones allowed.
  • volume β€” pointer of lsm_volume. like, the volume you're obsessed with.
  • pdc β€” uint32_t. this is your physical disk cache setting, and the valid values are literally only these two:
    • LSM_VOLUME_PHYSICAL_DISK_CACHE_ENABLED β€” enable physical disk cache ✨
    • LSM_VOLUME_PHYSICAL_DISK_CACHE_DISABLED β€” disable physical disk cache πŸ’€
  • flags β€” reserved for future use, so you must pass LSM_CLIENT_FLAG_RSVD. no free styling, bestie.

⭐ VERSION ⭐

1.3 β€” yeah she's been around a minute, lowkey iconic for it. πŸ‘‘


🌈 DESCRIPTION 🌈

so basically, this function changes the setting of the RAM physical disk cache of the specified volume. that's the vibe.

but here's the tea you need to know: on some products (like HPE SmartArray), this action is effective at system level. which means even if you're requesting a change on just one specified volume, the change will apply to all other volumes on the same controller(system). so it's giving "i only asked for one" but the system said "no babe, we're doing all of them". 😭 not a drill, be aware.


🧚 CAPABILITY 🧚

  • LSM_CAP_VOLUME_PHYSICAL_DISK_CACHE_UPDATE
  • LSM_CAP_VOLUME_PHYSICAL_DISK_CACHE_UPDATE_SYSTEM_LEVEL

πŸ’œ RETURN πŸ’œ

error code as enumerated by lsm_error_number, and here's the whole menu:

  • LSM_ERR_OK β€” on success. slay. πŸŽ‰
  • LSM_ERR_NOT_FOUND_VOLUME β€” when volume not found. she's not here, hun. πŸ™ˆ
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL or the flags are invalid. read the instructions pls. 😀
  • LSM_ERR_NO_SUPPORT β€” not supported. the system simply said no. πŸ’€

ngl bestie, watch out for that system-level thing up in DESCRIPTION β€” it's the plot twist of this whole manpage. 🫢

and that's the whole page! this was the Libstoragemgmt C API Manual entry lsm_volum...che_update(3), dated February 2026, and the footer's really just lsm_volume_physical_disk_cache_uplsm_volum...che_update(3) being its cute little self. mwah. πŸ’‹βœ¨πŸŒΈ

πŸ“¦ where this page comes from