lvm2 and VDO will it blend ?
summary
LVM2 adds a vdo target so LVM can create and manage VDO devices (lvcreate type vdo / vdo-pool), using the vdo kernel modules and vdo tools (vdoformat/vdostart) on Fedora/rawhide. VDO uses fixed 4K blocks and performs deduplication and compression on those blocks; metadata lives in a filesystem file. Current implementation exposes a single VDO LV per pool, supports resizing (can reduce virtual LV but data is discarded), works in a demo (dedupe observed) but is slower than plain volumes.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:04Agenda
- 1:45News
- 5:30Installation
- 6:10Thin provisioning
- 8:43Video commands
- 10:59Terminology
- 11:42Devices
- 13:50Basic commands
- 19:09Testing
related talks
39mThe Power of the Device Mapper - From Dm-cache To Dm-zoned
27mEstimating dm-vdo storage savings
48mSoftware Defined Storage the Linux way
18mDm-qcow2: qcow2 as Device-mapper Block Device
24mvDPA Support in Linux Kernel
26mUsing LVM writecache for faster write performance
18mvdpa-blk: Unified Hardware and Software Offload for virtio-blk
13mManage storage easily with Linux System Roles