Hello,
thanks for the hint. I opened a ticket with a feature request to include
the ec-profile information in the output of ceph osd pool ls detail.
http://tracker.ceph.com/issues/40009
Rainer
Am 22.05.19 um 17:04 schrieb Jan Fajerski:
> On Wed, May 22, 2019 at 03:38:27PM +0200, Rainer Krienke
On Wed, May 22, 2019 at 03:38:27PM +0200, Rainer Krienke wrote:
Am 22.05.19 um 15:16 schrieb Dan van der Ster:
Yes this is basically what I was looking for however I had expected that
its a little better visible in the output...
Mind opening a tracker ticket on http://tracker.ceph.com/ so we
Am 22.05.19 um 15:16 schrieb Dan van der Ster:
Yes this is basically what I was looking for however I had expected that
its a little better visible in the output...
Rainer
>
> Is this what you're looking for?
>
> # ceph osd pool ls detail -f json | jq .[0].erasure_code_profile
> "jera_4plus2"
On Wed, May 22, 2019 at 3:03 PM Rainer Krienke wrote:
>
> Hello,
>
> I created an erasure code profile named ecprofile-42 with the following
> parameters:
>
> $ ceph osd erasure-code-profile set ecprofile-42 plugin=jerasure k=4 m=2
>
> Next I created a new pool using the ec profile from above:
>
CRUSH only specifies where the chunks are placed, not how many chunks there
are (the pool specifies this)
This is the same with replicated rules: pool specifies the number of
replicas, the rule where they are put.
You can use one CRUSH rule for multiple ec pools
Paul
--
Paul Emmerich
Looking
Hello,
I created an erasure code profile named ecprofile-42 with the following
parameters:
$ ceph osd erasure-code-profile set ecprofile-42 plugin=jerasure k=4 m=2
Next I created a new pool using the ec profile from above:
$ ceph osd pool create my_erasure_pool 64 64 erasure ecprofile-42
The
