On 09/01/2026 14:22, Loïc Tortay via ceph-users wrote:

On 09/01/2026 13:15, Chris Palmer via ceph-users wrote:

...

I have a squid package-installed test cluster that I am trying to adopt into cephadm.

Monitors & managers have been adopted, and the orchestrator is functioning.

When I try to adopt an OSD though (e.g. osd.0), cephadm creates the new directory (<fsid>/osd.0) and populates the files from the legacy directory. It then crashes complaining that the directory osd/ceph-0 is not empty so cannot be removed. In some cases none of the files have been removed, and in others the block symlink and require_osd_release file remain. I can remove the new <fsid>/osd.0 and use ceph-volume to activate the OSD again.

cephadm.log reports that every file has been moved and the ownership set - even for files that still remain in the legacy directory. It doesn't report any other errors (apart from the directory not empty error. when it crashes).

I really can't find where to go from here. Any pointers appreciated...

Hello, We've had the same issue, with clusters initially installed/managed with Ceph-Ansible.

The issue (w/ Ceph-Ansible) seems to be related to some failure during the initial configuration which left multiple mounts on the same "/var/lib/ceph/$CLUSTERID/osd.$OSD" directory (it's an active mountpoint therefore it can't be removed).

Of course this is the "/var/lib/ceph/osd/ceph-$OSD" directory which has multiple mounts, not the one used by the container. Loïc.-- | Loīc Tortay <tortay@cc.in2p3.fr> - IN2P3 Computing Centre |