On 01/10/2014 05:13 AM, YIP Wai Peng wrote:
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.fa0000000active+remapped2014-01-10
11:18:53.1478420'06452:4272[7][7,3]0'02014-01-09
11:37:18.2022470'02014-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
# idweighttype nameup/downreweight
-140root default
-73datacenter CR2
-53host ceph3
61osd.6up1
71osd.7up1
81osd.8up1
<snip>
-93datacenter COM1
-66room 02-WIRECEN
-43host ceph2
31osd.3up1
41osd.4up1
51osd.5up1
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?
Try:
$ ceph pg 1.fa query
That will tell you the cause of why the PG is stuck.
- Peng
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
