On 11.03.2022 14:04, Ilya Dryomov wrote:
On Fri, Mar 11, 2022 at 8:04 AM Kai Stian Olstad <ceph+list@xxxxxxxxxx>
wrote:
Isn't namespace supported with erasure encoded pools?
RBD images can't be created in EC pools, so attempting to create RBD
namespaces there is pointless. The way to store RBD image data in
an EC pool is to create an image in a replicated pool (possibly in
a custom namespace) and specify --data-pool:
$ rbd namespace create --pool rep3 --namespace testspace
$ rbd create --size 10G --pool rep3 --namespace testspace --data-pool
ec42 --image testimage
This worked like a charm.
The image metadata (header object, etc) would be stored in rep3
(replicated pool), while the data objects would go to ec42 (EC pool).
I see the meta pool is using OMAP so I guess that's the reason it need
to be a replicated pool, makes sense.
Thank you for the help Ilya.
--
Kai Stian
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
