The Power of the Device Mapper - From Dm-cache To Dm-zoned
summary
Device mapper is the kernel layer for stacking virtual block devices and is controlled with low‑level commands like dmsetup create/remove/message/suspend/resume; most users drive it via LVM or cryptsetup while only ~10–15% use dmsetup directly. The new VDO target arrives mainline in kernel 6.9 and delivers dedupe+compression+thin provisioning (LZ4 compression, per‑volume slabs default 2 GB, up to 8,000 slabs, metadata reserve ≥3 GB), plus targets for caching, zoned devices and debug tools like dm_dust and dm_flakey.
AI-written summary · about
chapters (9)
- 0:00Introduction and agenda
- 2:37Storage stack overview
- 7:25Device mapper architecture
- 9:46Working with dmsetup
- 12:17Production targets overview
- 15:33Deep dive into VDO
- 31:22Additional production targets
- 32:58Debugging targets and conclusion
- 36:48Q&A and closing
related talks
27mSupporting non-power of 2 zoned devices
18mDm-qcow2: qcow2 as Device-mapper Block Device
21mAdvanced block storage test devices
03mZoned MC Conference Kick Off
25mUsing Zoned Block Devices in Fedora
31mHardware Friendly Vhost vDPA: Towards an Efficient and Migratable Device Model
25mlvm2 and VDO will it blend ?
52mPeeling Back the Layers of Storage