And in the tracker you never mentioned to add a symlink, only to add
the prefix "/rootfs" to the ceph config. I could have tried that
approach first. ;-)
Zitat von Eugen Block :
Alright, I updated the configs in our production cluster and
restarted the OSDs (after removing the manual mapp
Alright, I updated the configs in our production cluster and restarted
the OSDs (after removing the manual mapping from their unit.run
files), everything good.
@Zac: Would you agree that it makes sense to add this to the docs [1]
for cephadm clusters? They only cover the legacy world.
Tha
Yeah, now that you mention it, I recall figuring that out also at some point. I
think I did it originally when I was debugging the problem without the
container.
From: Eugen Block
Sent: Friday, May 3, 2024 8:37 AM
To: Wyll Ingersoll
Cc: ceph-users@ceph.io
Su
Hm, I wonder why the symlink is required, the OSDs map / to /rootfs
anyway (excerpt of unit.run file):
-v /:/rootfs
So I removed the symlink and just added /rootfs to the crush location hook:
ceph config set osd.0 crush_location_hook
/rootfs/usr/local/bin/custom_crush_location
After OSD r
Thank you!
From: Eugen Block
Sent: Friday, May 3, 2024 6:46 AM
To: Wyll Ingersoll
Cc: ceph-users@ceph.io
Subject: Re: [ceph-users] cephadm custom crush location hooks
I found your (open) tracker issue:
https://tracker.ceph.com/issues/53562
Your workaround work
I found your (open) tracker issue:
https://tracker.ceph.com/issues/53562
Your workaround works great, I tried it in a test cluster
successfully. I will adopt it to our production cluster as well.
Thanks!
Eugen
Zitat von Eugen Block :
Thank you very much for the quick response! I will take
Thank you very much for the quick response! I will take a look first
thing tomorrow and try that in a test cluster. But I agree, it would
be helpful to have a way with cephadm to apply these hooks without
these workarounds. I'll check if there's a tracker issue for that, and
create one if n
I've found the crush location hook script code to be problematic in the
containerized/cephadm world.
Our workaround is to place the script in a common place on each OSD node, such
as /etc/crush/crushhook.sh, and then make a link from /rootfs -> /, and set the
configuration value so that the
