VDOREADONLY(8)
π VDOREADONLY β the vdoreadonly(8) era π
okay bestie, so this is a System Manager's Manual page, section 8, and it's literally just called vdoreadonly. that's the whole name. it's giving "i do one thing and i do it slayfully" and honestly? respect. π«Ά
β¨ NAME β¨
vdoreadonly β puts a VDO device into read-only mode π
β¨ SYNOPSIS β¨
vdoreadonly filename
that's it. one arg. no flags required. we love a low-maintenance icon. π
β¨ DESCRIPTION β¨
so basically, vdoreadonly forces an existing VDO device into read-only mode. no cap, that's the entire job. it does not do anything else. it is not here to be versatile, it is here to be correct. π
filename must be the path of the VDODataLV, exactly as described over in lvmvdo(7). like, that's non-negotiable, bestie.
and here's the tea β: lvchange(8) will only mount that thing as read-only, so if you actually want a writable version of the device you have to manually create it yourself. the example below walks you through it step by step, so don't panic, we got you. πΈ
β¨ OPTIONS β¨
--helpβ prints this help message and then dips out. that's it. it said "here's the info, bye" π--versionβ shows you the version ofvdoreadonly. so you can be like "what version am i running" and it will simply tell you. iconic behaviour. β
β¨ EXAMPLE β¨
this is the whole little ritual, in order, exactly like this:
# 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`"
# vdoreadonly /dev/mapper/vdo1-vdo0pool_vdata
# dmsetup remove vdo1-vdo0pool_vdata
see how we activate it, dump the table to a file, deactivate it, recreate it with that saved table (that's the manual writable-version step from up there β¬οΈ), run vdoreadonly on it, and then clean up with dmsetup remove? chef's kiss. π₯ don't skip steps, fr fr. π
β¨ SEE ALSO β¨
lvmvdo(7), lvchange(8), dmsetup(8)
go read those too, they're the supporting cast and they ate. π¦
and that's the page!! Red Hat made this one, and this version is from 2023-04-14 β yes that date is giving "a while ago" but the info still hits. anyway ily, go forth and make your VDO device read-only responsibly ππ§π
π¦ where this page comes from
- centos-stream 10: vdo-support 8.3.2.1-1.el10 Β· GPL-2.0-only
- centos-stream 9: vdo-support 8.2.2.2-1.el9 Β· GPLv2
- debian trixie: vdo 8.3.1.1-1 Β· GPL-2.0-or-later
- fedora 43: vdo-support 8.3.0.73-2.fc43 Β· GPL-2.0-only
- fedora 44: vdo-support 8.3.2.1-2.fc44 Β· GPL-2.0-only
- nixos 26.05: vdo 8.3.2.1
- nixpkgs unstable: vdo 8.3.2.1
- ubuntu questing: vdo 8.3.1.1-1
- ubuntu resolute: vdo 8.3.1.1-1build1 Β· GPL-2.0-or-later
- ubuntu stonking: vdo 8.3.1.1-1build1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms