mirror of
https://github.com/versity/scoutfs.git
synced 2026-08-15 19:56:36 +00:00
Auke Kok
4661181496
The iomap read/write entry points have grown arguments that el10 has picked up. Since v5.18-rc7-162-g786f847f43a5 iomap_dio_rw() takes a private pointer that it stashes in the iomap_iter for the filesystem's use, and since v6.16-rc1-11-g2a5574fc57d1 the iomap_folio_ops that used to hang off the iomap are passed to iomap_file_buffered_write() as iomap_write_ops, which also gained a private pointer of its own. We have neither per-iter state nor write ops, so the compat wrappers just pass nulls for the new arguments, which the iomap code checks for. While we're in here, drop the extern for scoutfs_iomap_page_ops. It was never defined, and struct iomap_page_ops no longer exists upstream. Signed-off-by: Auke Kok <auke.kok@versity.com>
Introduction
scoutfs is a clustered in-kernel Linux filesystem designed to support large archival systems. It features additional interfaces and metadata so that archive agents can perform their maintenance workflows without walking all the files in the namespace. Its cluster support lets deployments add nodes to satisfy archival tier bandwidth targets.
The design goal is to reach file populations in the trillions, with the archival bandwidth to match, while remaining operational and responsive.
Highlights of the design and implementation include:
- Fully consistent POSIX semantics between nodes
- Atomic transactions to maintain consistent persistent structures
- Integrated archival metadata replaces syncing to external databases
- Dynamic seperation of resources lets nodes write in parallel
- 64bit throughout; no limits on file or directory sizes or counts
- Open GPLv2 implementation
Community Mailing List
Please join us on the open scoutfs-devel@scoutfs.org mailing list hosted on Google Groups