News › linux
By The Linux Camp News, October 31, 2026
The new lazyio mount option broadens activation of existing Ceph behavior. It targets workloads that tolerate relaxed cache coherency, rather than making lazy I/O a general-purpose recommendation.
Ceph's lazyio mount option entered Linus Torvalds's tree on October 30, 2026, as part of the updates targeting Linux 7.4-rc1. It enables existing lazy-I/O behavior across a mount instead of requiring activation for individual files through an ioctl, a file-control operation. The kernel pull-request tracker confirms the merge; this is development-tree integration, not a final Linux 7.4 release announcement. 2 3
According to Phoronix, the option applies lazy-I/O mode to all regular files when they are opened. That mode permits buffered I/O through the page cache even when several clients have the same file open for writing. The trade-off is relaxed cache coherency: applications must tolerate weaker coordination of cached file contents between clients. The maintainer's pull request confirms mount-wide activation but does not explain the precise coherency guarantees. 1 2
The practical change is the granularity of activation. A workload that wants lazy I/O throughout a mount can select it there rather than enabling it file by file. Phoronix identifies high-performance computing and similar coherency-tolerant workloads as the intended users. Neither that report nor the maintainer summary supplies benchmarks, so the supported benefit is simpler activation, not a measured throughput improvement. 2 1
Before selecting the option, review the coherency requirements of every application using the mount, not just the intended shared-file writers. This recommendation follows from the reported scope: activation covers all regular files at open time. A mount shared with applications requiring strict coherency is therefore outside the stated intended use case unless those requirements can be reconciled. 1
The sources retrieved on October 31 establish the merge and reported open-time scope, but leave deployment details unresolved. They do not establish remount behavior, treatment of already-open files, disable syntax or application synchronization requirements. Those details need authoritative option documentation or patch review before turning the announcement into a deployment procedure. 3 1