STRUCT LEAPRAID_RAIDVOL_P1(9)
π NAME π
okay so bestie, welcome to struct leapraid_raidvol_p1 β it's the RAID volume configuration page 1, and yes the "p1" is doing main character energy because there's a whole other page out there (hi struct leapraid_raidvol_p0, we see you π).
This is from the Kernel API Manual, and the man page itself is literally called struct leapraid_raidvol_p1(9) β iykyk, the (9) is the section for kernel stuff.
β¨ SYNOPSIS β¨
here's the whole vibe, copied exactly, no cap:
struct leapraid_raidvol_p1 {
struct leapraid_cfg_pg_header header;
__le16 dev_hdl;
u8 r1[42];
__le64 wwid;
u8 r2[8];
};
that's it, that's the struct π
π¦ Members π¦
headerβ the configuration page header. every page's gotta have one, it's giving "must-have accessory" πdev_hdlβ the device handle of the RAID volume. this is how you point at that volume specifically, like tagging someone in the group chat π«Άr1β reserved. literally justu8 r1[42]sitting there being quiet. 42 bytes of "don't touch, not for you" πwwidβ the world-wide identifier for the volume. as the name suggests, it's the volume's global ID, its passport, its @ handle across the whole world πr2β also reserved.u8 r2[8]this time. more reserved bytes, more "nothing to see here" energy β¨
heads up bestie:r1andr2are reserved β the man page does not tell us what they're for, so don't go inventing meaning for them, mmkay? π
π₯ SEE ALSO π₯
the man page points you at the kernel file ./drivers/scsi/leapraid/leapraid.h, and honestly the friend group here is huge β grab a snack, this is a long one π
struct leapraid_reg_base(9)struct leapraid_atomic_req_desc(9)union leapraid_rep_desc_union(9)struct leapraid_req(9)struct leapraid_rep(9)struct leapraid_sge_simple32(9)struct leapraid_sge_simple64(9)struct leapraid_sge_simple_union(9)struct leapraid_sge_chain_union(9)struct leapraid_ieee_sge_simple32(9)struct leapraid_ieee_sge_simple64(9)union leapraid_ieee_sge_simple_union(9)union leapraid_ieee_sge_chain_union(9)struct leapraid_chain64_ieee_sg(9)union leapraid_ieee_sge_io_union(9)union leapraid_simple_sge_union(9)union leapraid_sge_io_union(9)struct leapraid_cfg_pg_header(9)struct leapraid_cfg_ext_pg_header(9)struct leapraid_cfg_req(9)struct leapraid_cfg_rep(9)struct leapraid_boot_dev_format_sas_wwid(9)struct leapraid_boot_dev_format_enc_slot(9)struct leapraid_boot_dev_format_dev_name(9)union leapraid_boot_dev_format(9)struct leapraid_manufacturing_p0(9)struct leapraid_bios_page2(9)struct leapraid_bios_page3(9)struct leapraid_raidvol0_phys_disk(9)struct leapraid_raidvol_p0(9)struct leapraid_raidpd_p0(9)struct leapraid_sas_io_unit0_phy_info(9)struct leapraid_sas_io_unit_p0(9)struct leapraid_exp_p0(9)struct leapraid_exp_p1(9)struct leapraid_sas_dev_p0(9)struct leapraid_sas_phy_p0(9)struct leapraid_enc_p0(9)struct leapraid_raid_cfg_p0_element(9)struct leapraid_raid_cfg_p0(9)union leapraid_mpi_scsi_io_cdb_union(9)struct leapraid_mpi_scsiio_req(9)union leapraid_scsi_io_cdb_union(9)struct leapraid_scsiio_req(9)struct leapraid_scsiio_rep(9)struct leapraid_scsi_tm_req(9)struct leapraid_scsi_tm_rep(9)struct leapraid_sep_req(9)struct leapraid_sep_rep(9)struct leapraid_adapter_init_req(9)struct leapraid_rep_desc_q_arr(9)struct leapraid_adapter_init_rep(9)struct leapraid_adapter_log_req(9)struct leapraid_adapter_log_rep(9)struct leapraid_adapter_features_req(9)struct leapraid_adapter_features_rep(9)struct leapraid_scan_dev_req(9)struct leapraid_scan_dev_rep(9)struct leapraid_evt_notify_req(9)struct leapraid_evt_notify_rep(9)struct leapraid_evt_data_sas_dev_status_change(9)struct leapraid_evt_data_ir_change(9)struct leapraid_evt_data_sas_disc(9)struct leapraid_evt_sas_topo_phy_entry(9)struct leapraid_evt_data_sas_topo_change_list(9)struct leapraid_evt_data_sas_enc_dev_status_change(9)struct leapraid_io_unit_ctrl_req(9)struct leapraid_io_unit_ctrl_rep(9)struct leapraid_raid_act_req(9)struct leapraid_raid_act_rep(9)struct leapraid_smp_passthrough_req(9)struct leapraid_smp_passthrough_rep(9)struct leapraid_sas_io_unit_ctrl_req(9)
that's 73 neighbors bestie, the whole extended family showed up to the function π§
and that's the page! πΈ sourced from ./drivers/scsi/leapraid, dated October 2026, and signed off as struct leapraid_raidvol_p1(9) β slay, go read the header file, periodt π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms