Using Linux Block Integrity in Building and Testing Storage Systems
summary
Brings Linux block integrity into real storage stacks: enables SCSI/NVMe protection fields, uses target core with a file-backed backend and loop devices for development, and passes integrity into VMs via qemu 3.1 so CI can exercise shared drives. Finds only 2 bytes metadata on commodity drives, needs Broadcom driver masks to expose fields, fixes bugs (reference tag increments for 4K segments, NVMe 32+1 metadata page limit, and large-request splitting), and notes generic checksum is ~100 ops/s while Power-specific code is ~100x faster.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:33Storage Appliance
- 1:21Data Integrity
- 2:09Extended Sector
- 3:14Modern Industry
- 3:43Data Integrity Field
- 4:07Multiple Integrity Fields
- 4:25Eris
- 5:10Formatting
- 6:39Type 1 Protection
- 7:55Type 4 Protection
- 8:13Application Tag
- 9:44Drive
- 10:59Integrity Protection
- 11:53Casa Targets
- 12:40SATA Drive
- 12:59Old Skies
- 13:22Testing
- 13:53Testing NVMe
- 14:37Testing NVMe with Shared Drives
- 18:23Results
- 20:05Block Integrity Errors
- 22:55NVME Drives
- 24:46Performance
- 25:42Wrapup
- 26:37Feedback
- 29:45Requests Splits
related talks
14mAdvancing Data Integrity in Linux
44mVM block error injection, a novel approach for testing Linux storage
21mAdvanced block storage test devices
45mLinux Storage Stack Explained
36mOverview and Recent Developments: Linux Integrity
26mIntegrity
24mLatest storage status on Arm
42mProtecting the Linux Kernel from Confidential Computing Threats in Virtual Environments