nilfs_ioctl_move_blocks(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nilfs_ioctl_move_blocks — a kernel API manual, but make it make sense

okay so bestie, welcome to the Kernel API Manual ✨ and specifically to nilfs_ioctl_move_blocks, aka the little function that does the actual heavy lifting while the garbage collector is out here being a main character 🗑️👑

🌸 NAME 🌸

nilfs_ioctl_move_blocks — moves a valid inode's blocks during garbage collection, no cap 🧹✨

🦋 SYNOPSIS 🦋

int nilfs_ioctl_move_blocks (struct super_block *sb , struct nilfs_argv
*argv , void *buf );

literally that's the whole signature, she's not complicated 💅

🎀 ARGUMENTS 🎀

  • sb — the superblock object, your classic superblock situation 🫶
  • argv — a vector of arguments that came straight from userspace, hi bestie 👋
  • buf — an array of nilfs_vdesc structures, this is the good stuff 🍓

✨ DESCRIPTION ✨

so here's the tea ☕: nilfs_ioctl_move_blocks reads valid data/node blocks — the ones the garbage collector pointed at using that array of nilfs_vdesc structures — and then it stores them into the page caches of GC inodes. that's it. that's the whole vibe. it's giving "relocating your faves so nothing gets lost" 🦋💖

🔥 RETURN 🔥

on success you get the number of processed nilfs_vdesc structures — slay, a count, we love a countable win 👑 — or a negative error code if it went sideways 😭💀

🌈 SEE ALSO 🌈

the whole friend group, fr fr — kernel file ./fs/nilfs2/ioctl.c and then:

and that's the page!! 💜 this one lives in ./fs/nilfs2, dated October 2026, and yes the header said nilfs_ioctl_move_blocks(9) the whole time — iykyk 🧚✨ bye bestie, go read some blocks 🎀

📦 where this page comes from