Dear all,
I have some pgs that are stuck_unclean, I'm trying to understand why.
Hopefully someone can help me shed some light on it.
For example, one of them is
# ceph pg dump_stuck unclean
1.fa 0 0 0 0 0 0 0 active+remapped 2014-01-10 11:18:53.147842 0'0 6452:4272
[7] [7,3] 0'0 2014-01-09 11:37:18.202247 0'0 2014-01-09 11:37:18.202247
My pool 1 looks like this
pool 1 'metadata' rep size 2 min_size 1 crush_ruleset 3 object_hash
rjenkins pg_num 256 pgp_num 256 last_change 2605 owner 0
The rule 3 is
rule different_host {
ruleset 3
type replicated
min_size 1
max_size 10
step take default
step chooseleaf firstn 0 type host
step emit
}
My osd tree looks like
# id weight type name up/down reweight
-1 40 root default
-7 3 datacenter CR2
-5 3 host ceph3
6 1 osd.6 up 1
7 1 osd.7 up 1
8 1 osd.8 up 1
<snip>
-9 3 datacenter COM1
-6 6 room 02-WIRECEN
-4 3 host ceph2
3 1 osd.3 up 1
4 1 osd.4 up 1
5 1 osd.5 up 1
osd.7 and osd.3 are in different hosts, so the rule is satisfied. Why is it
still in the 'remapped' status, and what is it waiting for?
- Peng
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
