and it's not only possible because of a
> false detection from one of the above sources, but also, I think can
> come from "dead" daemons being referenced in CRUSH.
>
> You might want to run through this lists's history for "phantom host"
> postings
hough.
> Is this key present?
>
> ceph config-key get mgr/cephadm/host.cephfs-cluster-node-2 | jq
>
> Is the VM still reachable? If it is, check the MON directory under
> /var/lib/ceph/{FSID}/mon.X and remove it. You can also first check
> with 'cephadm ls --no-detail' if ce
Hello,
I'm pretty new to ceph deployment. I have setup my first cephfs cluster
using cephadm. Initially, I deployed ceph in 3 virtualbox instances that I
called cephfs-cluster-node-{0, 1, 2} just to test things. Later, I added 5
more real hardware nodes. Later I decided I'd remove the virtualboxes
