Hello all Thanks for your reply.
I already tried few things.. 1. Tried deleting the old ec profile and thought to create it with same name but with osd failure domain, it did not allow deleting from pool. 2. Changed crush rule with osd too. It reverted automatically to host. 3. Then Created new ec profile and created a new rule with it and set it to pools, shows attached too. But pool still shows old EC profile attached which is with host failure domain, 4. Tried pausing osd read/write and then tried to delete the profile but no luck. 5. Replicated pool is easy to change in rush map directly which is great. But seems issue with EC pool profile. Now the last option which I see is to migrate the data by crating new pool with new osd failure profile which seems a long time consuming process(may need down time), not looking for it, Do we see any other way? Regards Dev > On Feb 5, 2025, at 1:27 AM, Frédéric Nass <[email protected]> > wrote: > > Hi Jane, > > I totally agree with you and Eugen about not using 'osd' as a failure domain, > but the initial question was about the profile. ;-) > > Cheers, > Frédéric. > > ----- Le 5 Fév 25, à 10:16, Janne Johansson [email protected] a écrit : > >>> Hi Dev, >>> >>> You can't. There's no 'ceph osd erasure-code-profile modify' command and the >>> 'ceph osd erasure-code-profile set' will fail on output below when run on an >>> existing profile. See below: >> >> I think you are answering the wrong question. >> >> You are right that one cannot change the EC profile, but you can >> change the crush rules, so that the failure domain changes from "host" >> to "osd" which is what I think was asked for, not changing the EC >> profile. >> >> I agree with Eugene that it is a bad idea in the long run, but it can be >> done. >> >> >> -- >> May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
