Actions
Bug #8984
closedcreating erasure-code pool when not having a root item default
% Done:
0%
Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
5 - suggestion
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When creating a EC pool:
ceph osd pool create poolio 128 128 erasure profile15
It returns
Error ENOENT: root item default does not exist
Which is indeed true here, but by design, because I have multiple roots for sas and ssd pools.
I worked around it by manually putting the rule for this pool in my crushmap:
rule poolio { ruleset 2 type erasure min_size 3 max_size 20 step set_chooseleaf_tries 5 step take default-ec step choose indep 0 type osd step emit }
Updated by Loïc Dachary over 9 years ago
- Subject changed from creating EC pool when not having a root item default to creating erasure-code pool when not having a root item default
- Status changed from New to Won't Fix
- Assignee set to Loïc Dachary
The recommended way to deal with the absence of a default root is to define an erasure-code-profile that specifies the default root to be used with ruleset-root={root}
Updated by Greg Farnum almost 7 years ago
- Project changed from Ceph to RADOS
- Category deleted (
10)
Actions