VDODUMPBLOCKMAP(8)

📦 version 8.3.2.1, in centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu questing, ubuntu resolute, ubuntu stonking

💅 VDODUMPBLOCKMAP — the manual, but make it cute (section 8, bestie)

okay so this is vdodumpblockmap, straight out of the System Manager's Manual, and she's here to spill the tea on where your data actually lives. 🫶

✨ NAME ✨

vdodumpblockmap — dump the LBA->PBA mappings of a VDO device 🌸

🎀 SYNOPSIS 🎀

vdodumpblockmap [--lba=lba] filename

🦋 DESCRIPTION 🦋

okay so picture this: vdodumpblockmap dumps all the LBA->PBA mappings from a cleanly shut down VDO device — or, if you're feeling picky, just the specified one. main character energy either way. ✨

filename has to be the path of the VDODataLV, exactly as described over in lvmvdo(7). no cap, that's the whole vibe. 💖

💅 OPTIONS 💅

  • --help — print this help message and exit. the classic "bestie, just tell me what to do" move. 🙈
  • --lba — dump only the mapping for the specified LBA. selective queen behavior. 👑
  • --version — show the version of vdodumpblockmap. iykyk. 🌈

🔥 EXAMPLE 🔥

here's the little ritual, in order, no skips:

# lvchange -ay vdo1/vdo0pool_vdata
# vdodumpblockmap /dev/mapper/vdo1-vdo0pool_vdata
# lvchange -an vdo1/vdo0pool_vdata

activate, dump, deactivate. ate and left no crumbs. 💜

🌸 SEE ALSO 🌸

lvmvdo(7), lvchange(8)

fr fr, this page is from Red Hat, dated 2023-03-28. slay, stay iconic, and always shut your VDO device down cleanly before you dump its block map. 💖✨🎀
📦 where this page comes from