VDOFORCEREBUILD(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

💖 VDOFORCEREBUILD — okay so bestie, let's talk ✨

ngl this is vdoforcerebuild, section 8 of the System Manager's Manual, and she is the girl you call when your VDO device is stuck being dramatic in read-only mode. 🎀

🌸 NAME 🌸

vdoforcerebuild — prep a VDO device so it can finally exit read-only mode 💅

🦋 SYNOPSIS 🦋

vdoforcerebuild filename

✨ DESCRIPTION ✨

So here's the tea: vdoforcerebuild forces an existing VDO device to exit read-only mode, and makes it try to regenerate as much metadata as it possibly can. It's giving rescue mission. It's giving main character energy. 🔥

filename has to be the path of the VDODataLV as described in lvmvdo(7). Lowkey important: lvchange(8) will only mount that thing as read-only, so you have to manually create a writable version of that device yourself. The example down below shows you exactly how, no cap. 👑

💜 OPTIONS 💜

  • --help — prints this help message and then dips. ✌️
  • --version — shows you the version of vdoforcerebuild. that's it, that's the whole vibe. 💫

🍓 EXAMPLE 🍓

okay bestie, copy these exactly, fr fr:

# 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`"
# vdoforcerebuild /dev/mapper/vdo1-vdo0pool_vdata
# dmsetup remove vdo1-vdo0pool_vdata

like… look at her go. ate. 💅

🌈 SEE ALSO 🌈

and that's the whole page, bestie!! 🫶 this icon of a man page was brought to you by Red Hat, dated 2023-04-14, living under the name VDOFORCEREBUILD(8). go forth and un-read-only your life. 💖✨🌸

📦 where this page comes from