_scsih_mark_..._raid_device(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… _scsih_mark_..._raid_device β€” Kernel API Manual, bestie edition ✨

okay so picture this: it's a kernel API manual page, it's got a name longer than my attention span, and it lives in the 9 section. yeah. we're doing this. sit down, grab a strawberry πŸ“, and let's get into it.


🌸 NAME 🌸

_scsih_mark_responding_raid_device β€” mark a raid_device as responding πŸ’–

like literally that's the whole job. mark it. it's responding. slay.


✨ SYNOPSIS ✨

void _scsih_mark_responding_raid_device (struct MPT3SAS_ADAPTER *ioc ,
u64 wwid , u16 handle );

three args, returns void, zero drama. moving on πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ioc β€” the per adapter object. it's the adapter's whole personality, basically. every function in this file is obsessed with it.
  • wwid β€” the world wide identifier for the raid volume πŸ‘‘ it's the volume's government name.
  • handle β€” the device handle. short, sweet, does the identifying.

πŸ’œ DESCRIPTION πŸ’œ

so after a host reset, this function goes and finds out whether devices are still responding. that's it. that's the vibe check πŸ”₯

it's used in _scsih_remove_unresponsive_raid_devices β€” iykyk, the cleanup crew that yeets the devices that ghosted us πŸ’€

ngl this is a supporting-character function: it doesn't do the reset, it doesn't remove anything itself, it just marks the ones that came back so the removal pass knows who to leave alone. no cap.

🧚 SEE ALSO 🧚

the friend group is large. like, uncomfortably large. here's the full roster, no one left out, periodt:

like I said. huge friend group. but every single one of them showed up to the party 🫢


<div align="center">✿ ✿ ✿</div>

and that's the page, bestie! πŸŽ€ brought to you straight out of ./drivers/scsi/mpt3sas, dated October 2026, and yes the header still says _scsih_mark_..._raid_device(9) because the abbreviated name ate and left no crumbs πŸ’… see u in the next man page πŸ’–βœ¨

πŸ“¦ where this page comes from