On 26/07/24 12:35, Kai Stian Olstad wrote:
On Tue, Jul 23, 2024 at 08:24:21AM +0200, Iztok Gregori wrote:
Am I missing something obvious or with Ceph orchestrator there are non
way to specify an id during the OSD creation?
You can use osd_id_claims.
I tried the osd_id_claims in a yaml file
On 23/07/24 08:41, Robert Sander wrote:
On 7/23/24 08:24, Iztok Gregori wrote:
Am I missing something obvious or with Ceph orchestrator there are non
way to specify an id during the OSD creation?
Why would you want to do that?
For me there wasn't a "real need", I could ima
end I (re)added the OSD in the correct order, starting with
the lowest id device.
--
Iztok Gregori
ICT Systems and Services
Elettra - Sincrotrone Trieste S.C.p.A.
http://www.elettra.eu
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe
ervers will be drained
before been reinstalled, just to be sure to have a "fresh" start).
Have you any ideas and/or advice to give us?
Thanks a lot!
Iztok
P.S. I saw that the script cephadm doesn't support Rocky, I can modify
it to do so and it should work, but is there a plan t
the
right tool for what I want to achieve. But I didn't found a lot of
information about it, sombody knows something more, are those tools
"safe" to run in my case?
Thanks a lot
Iztok
Cheers
Boris
Am Mo., 16. Jan. 2023 um 15:01 Uhr schrieb Iztok Gregori
mailto:iztok.g
7.53 1.29 37 up
In this situation was the correct way to address the problem?
reweight-by-utilization the osd.60 to free up space (the OSD is a 6 TB
disk, and other OSD on the same host are nearfull)? There is other way
to manually map a PG to a different OSD?
Thank you for your attention
