As someone else mentioned, ‘ceph osd rm 0’ took it out of the osd tree.Crush map attached. Odd seeing deviceN in the devices block in the osd numbering holes in my cluster. Assume that is just a placeholder until it gets backfilled with an osd upon expansion.Thanks,Reed# begin crush map
tunable cho
Hi,
On 08/23/2016 08:19 PM, Reed Dier wrote:
Trying to hunt down a mystery osd populated in the osd tree.
Cluster was deployed using ceph-deploy on an admin node, originally 10.2.1 at
time of deployment, but since upgraded to 10.2.2.
For reference, mons and mds do not live on the osd nodes,
Please share the crushmap.
Thanks
Swami
On Tue, Aug 23, 2016 at 11:49 PM, Reed Dier wrote:
> Trying to hunt down a mystery osd populated in the osd tree.
>
> Cluster was deployed using ceph-deploy on an admin node, originally 10.2.1
> at time of deployment, but since upgraded to 10.2.2.
>
> For
Trying to hunt down a mystery osd populated in the osd tree.
Cluster was deployed using ceph-deploy on an admin node, originally 10.2.1 at
time of deployment, but since upgraded to 10.2.2.
For reference, mons and mds do not live on the osd nodes, and the admin node is
neither mon, mds, or osd.
