惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
D
DataBreaches.Net
博客园 - 三生石上(FineUI控件)
博客园_首页
T
Tailwind CSS Blog
美团技术团队
Hugging Face - Blog
Hugging Face - Blog
博客园 - 叶小钗
大猫的无限游戏
大猫的无限游戏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
云风的 BLOG
云风的 BLOG
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 聂微东
S
SegmentFault 最新的问题
小众软件
小众软件
酷 壳 – CoolShell
酷 壳 – CoolShell
N
Netflix TechBlog - Medium
Jina AI
Jina AI
WordPress大学
WordPress大学
U
Unit 42
J
Java Code Geeks
Blog — PlanetScale
Blog — PlanetScale
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog

OneUptime Blog

How to Monitor Azure App Services (PaaS) with OpenTelemetry Grafana Stack vs OneUptime: DIY Observability or Unified Platform? Your AI Workloads Are About to Blow Up Your Observability Bill The Great Observability Consolidation Is Here How to Write Custom Object Classes for Ceph How to Write Custom Ceph Manager Modules How to Write a ceph.conf Configuration File How to Use Rook-Ceph with OpenShift How to Use Rook-Ceph with Longhorn for Comparison How to Configure Volume Snapshot Class for RBD in Rook How to Configure VolumeReplicationClass Scheduling Intervals in Rook How to Set Up Volume Replication with Rook-Ceph How to Create Volume Group Snapshots with Rook CSI How to Visualize Ceph Network Performance in Grafana How to Enable Virtual Host-Style Bucket Access in Rook How to View Runtime Configuration via Admin Socket How to View Quota Settings and Update Stats in Ceph RGW How to View PG Scaling Recommendations with autoscale-status How to View PG Distribution via Admin Socket How to View Performance Metrics in the Ceph Dashboard How to View OSD Performance Counters in Ceph How to View Connection Status via Admin Socket How to View Ceph Cluster Summary Dashboard via CLI How to Version Control Rook-Ceph Configuration How to Version Control Ceph Infrastructure with Terraform How to Verify Kubernetes Node Requirements for Rook-Ceph Deployment How to Verify Health Before and After Rook Upgrades How to Verify Data Integrity with Deep Scrubbing How to Verify Complete Rook-Ceph Cleanup How to Verify Backup Integrity from Ceph Snapshots
How to Understand the undersized PG State in Ceph
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

The undersized PG state indicates that the acting set for a PG has fewer OSDs than the pool's size setting, but the PG has NOT fallen below the min_size threshold. The PG continues to serve I/O but with reduced replication.

undersized vs degraded

These two states are closely related but have distinct meanings:

StateMeaningI/O Status
degradedSome object replicas are missingActive, data missing
undersizedActing set is smaller than pool sizeActive, acting set reduced

A PG can be undersized without being degraded if the acting set is smaller than size but all objects in the acting set are consistent. Conversely, a PG can be degraded without being undersized.

What Causes undersized

  1. Not enough OSDs are available to fill the acting set
  2. Insufficient OSDs in a CRUSH failure domain
  3. Pool size is set higher than the available OSD count
# Check pool size settings
ceph osd pool get mypool size
ceph osd pool get mypool min_size

# Check how many OSDs are up
ceph osd stat

Checking Undersized PGs

ceph status
# HEALTH_WARN: X/Y pgs undersized

ceph pg stat | grep undersized

# Detailed list
ceph pg dump | grep undersized

For a specific PG:

ceph pg <pg-id> query | jq '{state: .state, acting: .acting, up: .up}'

Risk Assessment

Undersized PGs have less protection than configured. For a size 3 pool:

  • 2 acting OSDs: can lose 1 more OSD before data loss
  • 1 acting OSD: data is vulnerable
# Count undersized PGs by acting set size
ceph pg dump --format json | jq '.pg_stats[] | select(.state | contains("undersized")) | .acting | length' | sort | uniq -c

Resolving undersized

Add More OSDs

If the pool size exceeds available OSD count, add more OSDs:

ceph osd tree   # count available OSDs per host/rack

Reduce Pool Size

If the pool size is intentionally larger than available OSDs:

ceph osd pool set mypool size 2
ceph osd pool set mypool min_size 1

Recover Failed OSDs

If OSDs are down but recoverable:

systemctl start ceph-osd@<id>.service
watch ceph osd stat

Undersized During Maintenance

During rolling maintenance, undersized is expected and temporary. Set noout before starting:

ceph osd set noout
# Perform maintenance - PGs become undersized temporarily
# Restart OSDs
ceph osd unset noout
# PGs recover to full size

Summary

Undersized PGs have a smaller acting set than the configured pool size, which means reduced but not necessarily absent redundancy. The cluster continues serving I/O but with less fault tolerance. Resolve by adding OSDs, recovering downed ones, or adjusting the pool size to match the available hardware. During planned maintenance, this state is expected and transient.