Guides and notes on Ceph — clusters, OSDs, pools, RBD, CephFS and object storage.
Ceph is open-source software that stores your data across many ordinary servers, keeping copies so the data survives if a server fails. It provides block, file and object storage from one cluster.
These posts cover running it day to day: building clusters, OSDs and monitors, pools and CRUSH rules, and the RBD, CephFS and object storage interfaces.
FlashStore Against Crimson: Two Rewrites Of The Same OSD
Crimson is Ceph’s own rewrite of the OSD, in C++ on the Seastar framework, with a new native store called SeaStore; FlashStore is croit’s rewrite, in Rust, with a store of its own. Both are in preview and both are aimed at NVMe and fast networks. This compares them as Ceph 21.2.0 Umbrella ships Crimson, from Ceph’s source and documentation and croit’s ceph-rust snapshot: where each comes from and under what licence, why Rust meets the Five Eyes memory-safety guidance and C++ does not, why Crimson needs its own pools and an experimental flag while FlashStore drops into existing pools, why Umbrella has no way to turn an existing pool into a Crimson pool so the data has to be copied, what each tells the monitor at boot, Seastar reactors against pinned polling cores, the fact that a default Crimson OSD still runs BlueStore, SeaStore’s onode, OMAP and LBA trees against FlashStore’s one tree per shard, the order each commits a write in, SeaStore’s segment cleaner, and what hardware and pools each will take.
FlashStore Against Umbrella BlueStore: What croit Changed Under The OSD
croit’s ceph-rust is a clean-room Rust rewrite of the Ceph OSD with its own object store, FlashStore, in public preview since 9th November 2026. This puts it side by side with BlueStore exactly as Ceph 21.2.0 Umbrella ships it, read from both projects’ source and documentation: what is in the repository and under which licences, where each store keeps its metadata, how a 4 KiB write and a write under 4 KiB reach the drive in each, Umbrella’s thread pools against FlashStore’s one thread per core, why FlashStore makes power-loss protection a hard requirement, what it will not run on, why it tells your monitors it is BlueStore, which BlueStore options it honours and which it ignores, and why the only way between the two is backfill.
Who Actually Writes & Uses Ceph
I counted every commit to Ceph’s main branch for the last ten years — 69,613 of them from 1,718 people across 478 organisations — traced all 38 Steering Committee members to their employers, and gathered the publicly stated deployments. The result is a project that absorbed the loss of its founder and its second-largest contributor without dropping a beat, and is still shipping at the same rate today.