Using Zoned Block Devices in Fedora
summary
Shingled Magnetic Recording drives require sequential writes per zone and expose 256 MiB zones (example) that must be tracked with blk-zone report and reset commands, otherwise the kernel returns thousands of illegal unaligned write errors. Use the mq-deadline scheduler, create host-managed filesystems with f2fs -m or use the dm-zoned target; LVM needs pvcreate --dataalignment to align extents. Current limits: f2fs tops out near 16 TiB, consumer SMR drives reach ~14 TiB, RAID rebuilds can take a day or more and mdraid does not understand zones.
AI-written summary · about
chapters (11)
- 0:00Using Zoned Block Devices in Fedora
- 1:12What Is A Block Storage Device?
- 3:45Types of Zoned Block Devices
- 5:26Shingled Magnetic Recording Hard Disk Drives
- 6:22Ideal Applications for SMR Hard Disk Drives
- 7:55What DOESN'T Work With Zoned Block Devices?
- 9:58Using Zoned Block Devices in Linux (right now)
- 12:24The 'Rules of the Road of Zoned Block Devices
- 13:20Example of a Partial Zone Write
- 14:34Summary
- 15:52Questions?
related talks
23mImproving data placement for Zoned Linux File systems
27mSupporting non-power of 2 zoned devices
31mFrom Open-Channel SSDs to Zoned Namespaces
23mBtrfs RAID on zoned devices
03mZoned MC Conference Kick Off
25mZonefs: Features Roadmap
18mExperiences implementing zonefs support in ZenFS
21mAdvanced block storage test devices