diff options
| author | Michael Osipov <michaelo@FreeBSD.org> | 2026-09-13 19:55:28 +0000 |
|---|---|---|
| committer | Michael Osipov <michaelo@FreeBSD.org> | 2026-09-16 08:40:55 +0000 |
| commit | acdb2cdcd6ec6738c4f523df09ccd55404c6eb55 (patch) | |
| tree | 01b21d65ef79249f05531ad04d2e7731b6442b16 /sys/ofed/(public-mirror) | |
| parent | 32878e64e687a848fceb710ab9b45e396f27db3f (diff) | |
mfi_drive_name() built the "Exx:Syy" drive location string using
struct mfi_pd_info's encl_index field, the enclosure's firmware-
internal position index. Broadcom's own storcli/MegaCli tooling
instead leads with the enclosure's Device ID (EID) in its primary
drive listing; encl_index only shows up as "Position" in a detailed
per-enclosure view. Both numbers are raw, unmodified firmware values
already fetched into struct mfi_pd_info/mfi_pd_address, but only
encl_index was ever displayed or accepted as input, leading to
confusion when cross-referencing drive locations against storcli
output.
Switch mfi_drive_name() and mfi_lookup_drive() to use encl_device_id
instead, aligning FreeBSD's enclosure numbering with Broadcom's own
utilities. Since mrsasutil(8) is the same binary as mfiutil(8) under
a different name, this applies to both mfi(4) and mrsas(4) alike.
This is a user-visible behavior change: the numeric value of "xx" in
"Exx:Syy" now differs from before for any enclosure whose EID and
position index don't match, affecting anyone scripting against the
previous numbering.
PR: 294353
Reviewed by: imp
Relnotes: yes
Differential Revision: https://reviews.freebsd.org/D59654
Diffstat (limited to 'sys/ofed/(public-mirror)')
0 files changed, 0 insertions, 0 deletions
