Bug #54004
closedWhen creating erasure-code-profile incorrectly set parameters, it can be created successfully, and it can be used to create erasure crush rule
0%
Description
My osd tree is like below:
ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF
-7 0.19498 root mytest
-8 0.19498 host test_host
6 hdd 0.19498 osd.6 up 1.00000 1.00000
-1 1.17097 root default
-3 0.58600 host master
0 hdd 0.19499 osd.0 up 1.00000 1.00000
2 hdd 0.19499 osd.2 up 1.00000 1.00000
4 hdd 0.19499 osd.4 up 1.00000 1.00000
-5 0.58498 host node2
1 hdd 0.19499 osd.1 up 1.00000 1.00000
3 hdd 0.19499 osd.3 up 1.00000 1.00000
5 hdd 0.19499 osd.5 up 1.00000 1.00000
But when I created the erasure-code-profile, I specified the device type as ssd, and I can use it to successfully create an erasure crush rule
But when creating the replicated crush rule, specifying the wrong device type cannot create it successfully.
I would like to know what is the reason for this design
Updated by Neha Ojha about 2 years ago
- Has duplicate Bug #54005: Why can wrong parameters be specified when creating erasure-code-profile, and erasure crush rule can be created successfully added
Updated by Nitzan Mordechai almost 2 years ago
The profile can be created, but that doesn't mean that you will use it, yet.
as long as you are not using it, no error will appear, but when you try to create a pool with the profile, you will get the error.
Updated by Nitzan Mordechai almost 2 years ago
- Status changed from New to Rejected
- Assignee set to Nitzan Mordechai