VDOREGENERATEGEOMETRY(8)

💅 VDOREGENERATEGEOMETRY(8) 💅

okay bestie, so this whole page is about vdoregenerategeometry — a real one, from the System Manager's Manual section 8. sit down, hydrate, and let's get into it 🫶

---

✨ NAME ✨

vdoregenerategeometry — regenerate a VDO whose first few blocks have been wiped 😭

🦋 SYNOPSIS 🦋

vdoregenerategeometry [options...]  filename

🌸 DESCRIPTION 🌸

so picture this: your VDO device had a little accident and the beginning of the backing store got wiped. not the vibe. vdoregenerategeometry is gonna attempt to regenerate the geometry block of that VDO device. that's the whole gig ✨

⚠️ but listen — this tool will fail if enough of the device was wiped that the VDO super block got erased too. she can't work miracles. it also fails if there are multiple valid super block candidates chillin' on the volume, because then who's the main character? 🤷‍♀️

filename has to be the path of the VDODataLV as described in lvmvdo(7). and here's the tea: since lvchange(8) will only mount that as read-only, you gotta manually create a writable version of that device. the example below shows you exactly how, no cap 💅

if you already know where the super block lives — or you need to pick one of the candidate super blocks when multiple candidates got found — you can use the --offset option to specify the location (in bytes) of the super block on the backing store. iconic, honestly 💖

🎀 OPTIONS 🎀

• --help — print this help message and exit. classic, we love a clean exit 🦋
• --offset — specify the location (in bytes) of the super block. lowkey the most important one here ngl
• --version — show the version of vdoregenerategeometry. gotta know what you're working with, periodt 💅

🔥 EXAMPLE 🔥

here's the full sequence, copy it exactly, don't freestyle:

# lvchange -ay vdo1/vdo0pool_vdata
# dmsetup table vdo1-vdo0pool_vdata > vdata.table
# lvchange -an vdo1/vdo0pool_vdata
# dmsetup create vdo1-vdo0pool_vdata --table "`cat vdata.table`"
# vdoregenerategeometry /dev/mapper/vdo1-vdo0pool_vdata
# dmsetup remove vdo1-vdo0pool_vdata

like… the way that's a whole little ritual 😭 activate, dump the table, deactivate, recreate it writable, run the tool, then clean up after yourself. she's tidy. she's iconic. 🧚

🌈 SEE ALSO 🌈

lvmvdo(7), lvchange(8), dmsetup(8) — go read these too, iykyk 💜

---

okay that's the whole page bestie, go fix your VDO 🫶 this one came from Red Hat, dated 2023-04-14, and it lives at page VDOREGENERATEGEOMETRY(8). mwah 💋⭐