STRUCT UBI_AINF_VOLUME(9)

✨ struct ubi_ainf_volume(9) ✨

okay so this is a page from the Kernel API Manual bestie, and it's all about struct ubi_ainf_volume — literally the attaching information about a volume 💅 no cap, that's the whole vibe 🦋

---

🌸 NAME 🌸

struct ubi_ainf_volume — attaching information about a volume. that's it, that's the name, she's simple and she knows it ✨

---

🎀 SYNOPSIS 🎀

struct ubi_ainf_volume {
    int vol_id;
    int highest_lnum;
    int leb_count;
    int vol_type;
    int used_ebs;
    int last_data_size;
    int data_pad;
    int compat;
    struct rb_node rb;
    struct rb_root root;
 };

look at her. ten whole fields. main character energy 👑

---

🫶 Members 🫶

okay so let's go through the roster one by one, no skipping, we love a complete list 💖

• vol_id — the volume ID. her little name tag 🏷️
• highest_lnum — the highest logical eraseblock number in this volume. like the tallest number in the friend group 📏
• leb_count — how many logical eraseblocks are in this volume. the headcount fr fr 🔢
• vol_type — the volume type. that's it. that's the whole description 😭
• used_ebs — the number of used logical eraseblocks in this volume — and heads up, this one's only for static volumes, so don't come for her if she's blank on dynamic ones 🙈
• last_data_size — how much data is in the last logical eraseblock of this volume. and lowkey iconic detail: it's always equivalent to the usable logical eraseblock size in the case of dynamic volumes 💀✨
• data_pad — how many bytes at the end of this volume's logical eraseblocks are just... not used 🫠 (it's because of volume alignment, iykyk)
• compat — the compatibility flags of this volume. flags but make it compatible 🚩
• rb — the link in the volume RB-tree. she's the connector, the social butterfly 🌈
• root — the root of the RB-tree that contains all the eraseblocks belonging to this volume (those are struct ubi_ainf_peb objects, fyi 👀)

---

💜 Description 💜

so when you're attaching an MTD device, one object of this type gets allocated for each volume 🌟 that's the whole deal. one volume, one object, matching set, slay 🎀

---

🔥 SEE ALSO 🔥

go read the Kernel file ./drivers/mtd/ubi/ubi.h — it's giving homework but make it cute 📚 and also the whole squad:

• struct ubi_vid_io_buf(9)
• struct ubi_wl_entry(9)
• struct ubi_ltree_entry(9)
• struct ubi_rename_entry(9)
• struct ubi_fastmap_layout(9)
• struct ubi_fm_pool(9)
• struct ubi_eba_leb_desc(9)
• struct ubi_volume(9)
• struct ubi_volume_desc(9)
• struct ubi_debug_info(9)
• struct ubi_device(9)
• struct ubi_ainf_peb(9)
• struct ubi_attach_info(9)
• struct ubi_work(9)
• ubi_init_vid_buf(9)
• ubi_free_vid_buf(9)
• ubi_get_vid_hdr(9)
• ubi_ro_mode(9)
• vol_id2idx(9)
• idx2vol_id(9)
• ubi_is_fm_vol(9)
• ubi_find_fm_block(9)

---

bestie reminder: no invented facts on this page, every field above is exactly what the kernel docs say 💯

---

and that's the tea ☕ this came out of ./drivers/mtd/ubi, dated October 2026, and it's filed under struct ubi_ainf_volume(9) 🦋 mwah, go read the source, ily 💖✨