ubi_wl_scrub_peb(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

okay so bestie, this is ubi_wl_scrub_peb(9) from the Kernel API Manual — the page that exists to schedule a physical eraseblock for scrubbing 💅✨. That's the whole main-character assignment, no cap.

🌸 SYNOPSIS 🌸

int ubi_wl_scrub_peb (struct ubi_device *ubi , int pnum );

🎀 ARGUMENTS 🎀

  • ubi — the UBI device description object, aka the device context you're handing in 🫶
  • pnum — the physical eraseblock you want to schedule, periodt 🧚

✨ DESCRIPTION ✨

so here's the situation: when a bit-flip in a physical eraseblock gets detected, that physical eraseblock needs scrubbing. This function schedules a physical eraseblock for scrubbing, and the scrubbing itself is done in background — lowkey iconic, highkey efficient 🔥.

On success this function returns zero; on failure it returns a negative error code. That's the return vibe check: zero = slay, negative = error 😭.

bestie reminder: the scrub work is scheduled by this function, but it happens in background. The success/failure return is exactly zero / negative error code, no extra plot twist.

🌈 SEE ALSO 🌈

The source energy is Kernel file ./drivers/mtd/ubi/wl.c, and the SEE ALSO squad is literally:

made with 💖 from ./drivers/mtd/ubi — source/version vibes and date: October 2026 — and the page is ubi_wl_scrub_peb(9), periodt. bye bestie, go schedule that scrub 🦋✨

📦 where this page comes from