Re: Crushmap doesn't match osd tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mike,

I use a process like:

crushtool -c new-crushmap.txt -o new-crushmap && ceph osd setcrushmap -i new-crushmap

I did not attempt to validate your crush map. If that command fails, I would scrutinize your crushmap for validity/correctness.

Once you have the new crushmap injected, you can do something like:

ceph osd crush move ec02sv35 root=default datacenter=site-hd room=room-CR3.11391 rack=rack-9.41933-pehdpw09a


- Mike


On 4/25/2013 6:11 AM, Mike Bryant wrote:
Hi,
On version 0.56.4, I'm having a problem with my crush map.
The output of osd tree is:
# id    weight    type name    up/down    reweight

0    0    osd.0    up    1
1    0    osd.1    up    1
2    0    osd.2    up    1
3    0    osd.3    up    1
4    0    osd.4    up    1
5    0    osd.5    up    1

But there are buckets set in the crush map (Attached).

How can I fix this?
Editing the crush map and doing setcrushmap doesn't appear to change anything.

Cheers
Mike



_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux