Den tors 22 jan. 2026 kl 09:26 skrev Konstantin Shalygin via ceph-users <ceph-users@ceph.io>:

...

On 21 Jan 2026, at 16:58, Boris via ceph-users <ceph-users@ceph.io> wrote:

we want to migrate the data from a replicated to an EC pool. Is there a way to do it without downtime?

Your clients can move objects from one storage class to another, example s5cmd mv s3://bucket s3://bucket2 --storage-class="GLACIER"

Please correct me if I am wrong here (because I might totally be), but doesn't this leave some kind of "softlink" object in the old pool and "only" move the content over to the new pool? I seem to recall something like this when you move objects between storage pools/placements in ceph s3, and it could totally be about something else so don't take my word for it, but there is a nagging feeling in my mind there was some kind of situation where you still need to retain the old pool. Perhaps this is related to layering ceph pools (also one way in the past to move data from pool A to B while changing EC values or repl, not recommended anymore) which is why I am so unsure. If anyone wants to test/verify I am happy to be proven wrong. If I am wrong, then https://docs.ceph.com/en/latest/radosgw/placement/ has some good info on how to make more than one ceph pool available for rgw usage and set another one as the new default for users/buckets created after the change and so forth. -- May the most significant bit of your life be positive.