async_raid6_2data_recov(9)
π 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 arepandq. yup, the last two slots are reserved for the parity kings πoffsβ array of offset for pages inblocks. 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 π₯
- Kernel file
./crypto/async_tx/async_raid6_recov.c async_raid6_datap_recov(9)
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
- 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