VDODUMPMETADATA(8)

💾 VDODUMPMETADATA 💾

okay bestie, so this is the vdodumpmetadata page from section 8 of the System Manager's Manual, and it's genuinely so useful, let me put you on 💅

✨ NAME ✨

vdodumpmetadata — dump the metadata regions from a VDO device 🫶

🌸 SYNOPSIS 🌸

vdodumpmetadata [--no-block-map] [--lbn=lbn] vdoBacking outputFile

🦋 DESCRIPTION 🦋

so vdodumpmetadata dumps the metadata regions of a VDO device into another file, which is the whole point: it lets you save and transfer the metadata from a VDO without transferring the entire backing store. literally the glow-up of not hauling around a whole giant disk image for no reason ✨

vdoBacking has to be the path of the VDODataLV as described in lvmvdo(7). no substitutions, no vibes-based guessing, that exact path 💖

and heads up — vdodumpmetadata will produce a large output file. the expected size is roughly equal to VDO's metadata size. a rough estimate of the storage you need is 1.4 GB per TB of logical space. so like, clear some room first, bestie, this is not a small little guy 😭

🎀 OPTIONS 🎀

• --no-block-map — omit the block map. the output file will be of size no higher than 130MB + (9 MB per slab). smaller file, fewer things inside, you know how it is 💅
• --lbn — saves the block map page associated with the specified LBN in the output file. this option may be specified up to 255 times. implies --no-block-map. so like, if you only want a couple specific pages instead of the whole block map, this is your moment 👑

🔥 EXAMPLE 🔥

# lvchange -ay vdo1/vdo0pool_vdata
# vdodumpmetadata /dev/mapper/vdo1-vdo0pool_vdata vdo1-meta-dump
# lvchange -an vdo1/vdo0pool_vdata

activate, dump, deactivate. that's the whole little routine and it eats every time 🌈

👑 SEE ALSO 👑

lvmvdo(7), lvchange(8), vdodebugmetadata(8)

okay that's the whole page, you're so welcome 💜 this came to you from Red Hat, dated 2023-03-38, and it's the VDODUMPMETADATA(8) situation, periodt ✨🦋🌸