LLAPI_LAYO...E_COMP_DEL(3)

πŸ“¦ version 2.17.58, in ubuntu stonking

✨ llapi_layout_file_comp_del β€” bestie edition ✨

okay so this is a Lustre library function, manual section 3, and it lives in the Lustre Library Functions family. its whole job? deleting a layout component off a file that already exists. iconic behavior honestly πŸ’…


🌸 NAME 🌸

llapi_layout_file_comp_del β€” delete the specified layout component from an existing file.


πŸŽ€ SYNOPSIS πŸŽ€

#include <lustre/lustreapi.h>

int llapi_layout_file_comp_del(const char *path,
                               uint32_t id, uint32_t flags);

πŸ’– DESCRIPTION πŸ’–

So here's the tea: this function deletes the layout component(s) from a file that already exists. you point at them either by id or by flags, not both, okay? 🫢

Rules of the road, no cap:

  • id has to be a real unique component ID. like, an actual one. not vibes.
  • if you're passing flags instead, then id must be set to zero. periodt.
  • path is the file you're doing this to.

The flags you can use are:

  • LCME_FL_INIT β€” deletes the instantiated components in the layout.
  • LCME_FL_NEG|LCME_FL_INIT β€” deletes the uninstantiated components in the layout.

that's the whole menu, bestie. two options. choose wisely πŸ¦‹


🌈 RETURN VALUES 🌈

  • Returns 0 on success. slay. βœ…
  • Returns -1 if an error occurred β€” and in that case, errno is set appropriately. 😭

πŸ’€ ERRORS πŸ’€

  • EINVAL β€” an invalid argument was specified. you handed it something it cannot work with, bestie.
  • ENOENT β€” path doesn't exist, or the specified component isn't found in the file. it's giving "not here, never was" πŸ™ˆ

⭐ AVAILABILITY ⭐

llapi_layout_file_comp_del() is part of the lustre(7) user application interface library, and it's been in there since release 2.10.0. so if you're on something older… yeah, no. πŸ‘‘


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie πŸ’– this one's from the Lustre User API, dated 2024-08-27, filed under LLAPI_LAYO...E_COMP_DEL(3). go delete some components responsibly πŸŽ€βœ¨

πŸ“¦ where this page comes from