All articles
Comprehensive engineering guides for Ceph storage clusters, OSD daemon tuning, erasure coding pools, and CRUSH map placement rules.
Expanding a running cluster? Start with the guide to add an OSD to Ceph, which connects the device checks to deployment and rebalance verification.
-
Ceph Hardware Recommendations for Small Clusters
Ceph hardware recommendations for small clusters: CPU threads and RAM per OSD, PLP SSDs, 10 Gb/s networking, and why N100 boxes fall short.
-
How to Add an OSD to Ceph Safely with cephadm
Add a Ceph OSD without wiping the wrong disk: verify health, inventory the device, dry-run an OSD spec, deploy it, and watch the rebalance.
-
Ceph vs Gluster: Which to Choose for Your Cluster
Compare Ceph and GlusterFS by storage model, workload fit, hardware requirements, cluster size, and support outlook to choose the right platform.
-
Ceph Erasure Coding vs Replication: How to Choose
How erasure coding and replication differ in space amplification, failure tolerance and write cost, with a k+m overhead table and a rule for picking one.
-
Ceph Minimum Hardware Requirements: Nodes, CPU, RAM, Network
Learn why 3 nodes is the Ceph minimum, how many CPU threads and how much RAM each OSD needs, and the drive and 10 Gb/s network requirements.
-
Ceph HEALTH_WARN: Diagnose and Clear Warnings
A triage order for Ceph HEALTH_WARN covering degraded placement groups, nearfull OSDs, missed deep scrubs, autoscaler alerts and monitor clock skew.
-
Ceph Pools, Placement Groups and CRUSH Rules Explained
Configure Ceph pool size, inspect PG autoscaler recommendations and change a pool's CRUSH rule, with failure-domain checks before and after changes.