當檢查一個集羣的狀態時(執行ceph -w
或者ceph -s
),Ceph會彙報當前PG的狀態,每一個PG會有一個或多個狀態,最優的PG狀態是active + clean
。
下面是全部PG狀態的具體解釋:app
creatingide
Ceph is still creating the placement group.
Ceph 仍在建立PG。
activatingthis
The placement group is peered but not yet active.
PG已經互聯,可是尚未active。
activespa
Ceph will process requests to the placement group.
Ceph 可處理到此PG的請求。
clean日誌
Ceph replicated all objects in the placement group the correct
number of times.
PG內全部的對象都被正確的複製了對應的份數。
downcode
A replica with necessary data is down, so the placement group is
offline.
一個包含必備數據的副本離線,因此PG也離線了。
scrubbingorm
Ceph is checking the placement group metadata for inconsistencies.
Ceph 正在檢查PG metadata的一致性。
deep對象
Ceph is checking the placement group data against stored checksums.
Ceph 正在檢查PG數據和checksums的一致性。
degradedci
Ceph has not replicated some objects in the placement group the
correct number of times yet.
PG中的一些對象尚未被複制到規定的份數。
inconsistentrem
Ceph detects inconsistencies in the one or more replicas of an
object in the placement group (e.g. objects are the wrong size,
objects are missing from one replica *after* recovery finished,
etc.).
Ceph檢測到PG中對象的一份或多份數據不一致(好比對象大小不一直,或者恢復成功後對象依然沒有等)
peering
The placement group is undergoing the peering process
PG正在互聯過程當中。
repair
Ceph is checking the placement group and repairing any
inconsistencies it finds (if possible).
Ceph正在檢查PG而且修復全部發現的不一致狀況(若是有的話)。
recovering
Ceph is migrating/synchronizing objects and their replicas.
Ceph正在遷移/同步對象和其副本。
forced_recovery
High recovery priority of that PG is enforced by user.
用戶指定的PG高優先級恢復
recovery_wait
The placement group is waiting in line to start recover.
PG正在等待恢復被調度執行。
recovery_toofull
A recovery operation is waiting because the destination OSD is over
its full ratio.
恢復操做由於目標OSD容量超過指標而掛起。
recovery_unfound
Recovery stopped due to unfound objects.
恢復由於沒有找到對應對象而中止。
backfilling
Ceph is scanning and synchronizing the entire contents of a
placement group instead of inferring what contents need to be
synchronized from the logs of recent operations. Backfill is a
special case of recovery.
Ceph正常掃描並同步整個PG的數據,而不是從最近的操做日誌中推斷須要同步的數據,Backfill(回填)是恢復的一個特殊狀態。
forced_backfill
High backfill priority of that PG is enforced by user.
用戶指定的高優先級backfill。
backfill_wait
The placement group is waiting in line to start backfill.
PG正在等待backfill被調度執行。
backfill_toofull
A backfill operation is waiting because the destination OSD is over
its full ratio.
backfill操做由於目標OSD容量超過指標而掛起。
backfill_unfound
Backfill stopped due to unfound objects.
Backfill由於沒有找到對應對象而中止。
incomplete
Ceph detects that a placement group is missing information about
writes that may have occurred, or does not have any healthy copies.
If you see this state, try to start any failed OSDs that may contain
the needed information. In the case of an erasure coded pool
temporarily reducing min\_size may allow recovery.
Ceph 探測到某一PG可能丟失了寫入信息,或者沒有健康的副本。若是你看到了這個狀態,嘗試啓動有可能包含所需信息的失敗OSD,
若是是erasure coded pool的話,臨時調整一下`min_size`也可能完成恢復。
stale
The placement group is in an unknown state - the monitors have not
received an update for it since the placement group mapping changed.
PG狀態未知,從PG mapping更新後Monitor一直沒有收到更新。
remapped
The placement group is temporarily mapped to a different set of OSDs
from what CRUSH specified.
PG被臨時分配到了和CRUSH所指定的不一樣的OSD上。
undersized
The placement group has fewer copies than the configured pool
replication level.
該PG的副本數量小於存儲池所配置的副本數量。
peered
The placement group has peered, but cannot serve client IO due to
not having enough copies to reach the pool\'s configured min\_size
parameter. Recovery may occur in this state, so the pg may heal up
to min\_size eventually.
PG已互聯,可是不能向客戶端提供服務,由於其副本數沒達到本存儲池的配置值( min_size 參數)。
在此狀態下恢復會進行,因此此PG最終能達到 min_size 。
snaptrim
Trimming snaps.
正在對快照作Trim操做。
snaptrim_Wait
Queued to trim snaps.
Trim操做等待被調度執行
snaptrim_Error
Error stopped trimming snaps.
Trim操做由於錯誤而中止