Advancing Data Integrity in Linux
Anuj Gupta, Christoph Hellwig, Kanchan Joshi, Vikash Kumar, Javier González, Roshan R. Nair, Jinyoung Choi
Abstract
Standalone hardware-only or software-only methods fail to provide comprehensive coverage in detecting data corruption. End-to-end data protection (E2EDP) addresses this by carrying per-block protection information (PI) throughout the I/O stack, from the application through the system software to the storage device. Although devices have supported PI for more than a decade, Linux remains incomplete in its support and utilization of these capabilities.
This paper closes two fundamental gaps in the mainline Linux kernel and introduces a PI-aware filesystem design with implementation and evaluation. First, we add a new io_uring interface that allows applications to exchange integrity metadata alongside the data. Second, we add flexible PI placement in Linux's block-integrity enabling support for a device configuration that was otherwise rejected. Finally, we introduce Filesystem Protection Information (FS-PI), a PI-aware design direction in which filesystems generate and verify integrity metadata directly while leveraging PI-capable hardware. We implement FS-PI in two major filesystems: in XFS, FS-PI introduces native data checksumming, extending data-integrity guarantees for the first time; in BTRFS, FS-PI replaces the checksum tree with a lightweight path that reduces metadata traffic, write amplification, and device wear.
We evaluated the cost and gains of FS-PI in BTRFS and XFS. The evaluation shows that FS-PI improves BTRFS performance by 26%, reduces host CPU utilization by 58%, and reduces device writes by 52%, extending SSD lifetime by 23%.
Ask about this paper
Your agent reads all of it.
Lune indexed this paper to the last equation, along with the top-tier papers that cite it. Ask a question and the answer quotes them.
Your agent calls
Luneget_paper_fulltext
Free to start. No credit card required.
Terminal
Install the CLIlune papers fulltext b6f59550-5574-401e-8942-176caa2c496aBuilds on1
Related papers
- MadFS: Per-File Virtualization for Userspace Persistent Memory FilesystemsShawn Zhong, Chenhao Ye, Guanzhou Hu, Suyan Qu et al.FAST 2023 · 27 citations
- IPLFS: Log-Structured File System without Garbage CollectionJuwon Kim, Minsu Kim, Muhammad Danish Tehseen, Joontaek Oh et al.USENIX ATC 2022
- Oxbow: A Coordinated Architecture for Multi-Component File SystemsJongyul Kim, Jaehwan Lee, Inhoe Koo, Peizhe Liu et al.OSDI 2026
- Can Applications Recover from fsync Failures?Anthony Rebello, Yuvraj Patel, Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau et al.USENIX ATC 2020 · 19 citations
- Fast and Synchronous Crash Consistency with Metadata Write-Once File SystemYanqi Pan, Wen Xia, Yifeng Zhang, Xiangyu Zou et al.OSDI 2025
