async_raid6_2data_recov(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– async_raid6_2data_recov β€” Kernel API Manual, section 9 πŸ’–

okay so bestie, picture this: your RAID-6 array is out here living its best life, and then two data blocks just ghost you at the same time. this function is the friend who shows up with the rescue. it asynchronously calculates two missing data blocks, like, while other stuff is happening, because being efficient is main character energy. ✨


🌸 NAME 🌸

async_raid6_2data_recov β€” asynchronously calculate two missing data blocks 🫢


⭐ SYNOPSIS ⭐

struct dma_async_tx_descriptor * async_raid6_2data_recov (int disks ,
size_t bytes , int faila , int failb , struct page **blocks ,
unsigned int *offs , struct async_submit_ctl *submit );

πŸŽ€ ARGUMENTS πŸŽ€

  • disks β€” number of disks in the RAID-6 array. that's the whole squad, bestie. πŸ’…
  • bytes β€” block size. yes it's literally just how big the block is, no cap.
  • faila β€” first failed drive index. the first one that betrayed you 😭
  • failb β€” second failed drive index. and then a second one?? rude.
  • blocks β€” array of source pointers where the last two entries are p and q. yup, the last two slots are reserved for the parity kings πŸ‘‘
  • offs β€” array of offset for pages in blocks. like a little address book for your pages πŸ¦‹
  • submit β€” submission/completion modifiers. this is the vibe check for how the job gets sent off and how you find out it's done. ✨

πŸ”₯ SEE ALSO πŸ”₯


and that's the whole thing, bestie β€” no notes, you ate that. πŸ’–βœ¨

source: ./crypto/async_tx Β· dated October 2026 Β· go forth and recover your data blocks, iykyk πŸ§šπŸ’œ

πŸ“¦ where this page comes from