FS not created when using erasure coding
Bug #1895154 reported by
Liam Young
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Ceph-FS Charm |
Fix Released
|
High
|
James Page |
Bug Description
When the ceph-mon charm tries to create a new fs it fails if an erasure-coded data pool is being used. This is because the client tool requires a '--force' option as using an ec default data pool is not recommended *1 *2. The suggested approach is to use a replicated pool for metatdata and a replicated pool as the default data pool. The add an additional EC data pool. Access to the datapools is the specified by the client using xattrs.
*1 https:/
*2 https:/
Changed in charm-ceph-fs: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Liam Young (gnuoy) |
milestone: | none → 20.10 |
Changed in charm-ceph-fs: | |
assignee: | Liam Young (gnuoy) → James Page (james-page) |
Changed in charm-ceph-fs: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/751017
Review: https:/