Bug #43061
closedceph fs add_data_pool doesn't set pool metadata properly
0%
Description
maybe related to https://tracker.ceph.com/issues/36028
root@ceph-dev-build ~/ceph/build $ ./bin/ceph osd pool create test 1
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2019-11-29T00:16:15.153+0100 7fa7b35ad700 -1 WARNING: all dangerous and experimental features are enabled.
2019-11-29T00:16:15.253+0100 7fa7b35ad700 -1 WARNING: all dangerous and experimental features are enabled.
pool 'test' created
root@ceph-dev-build ~/ceph/build $ ./bin/ceph osd pool application enable test cephfs
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2019-11-29T00:16:30.657+0100 7f084ca39700 -1 WARNING: all dangerous and experimental features are enabled.
2019-11-29T00:16:30.761+0100 7f084ca39700 -1 WARNING: all dangerous and experimental features are enabled.
enabled application 'cephfs' on pool 'test'
root@ceph-dev-build ~/ceph/build $ ./bin/ceph fs add_data_pool a test
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2019-11-29T00:16:54.521+0100 7f1f8f622700 -1 WARNING: all dangerous and experimental features are enabled.
2019-11-29T00:16:54.613+0100 7f1f8f622700 -1 WARNING: all dangerous and experimental features are enabled.
added data pool 3 to fsmap
root@ceph-dev-build ~/ceph/build $ ./bin/ceph osd pool application get test
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2019-11-29T00:17:11.977+0100 7fbcc4c72700 -1 WARNING: all dangerous and experimental features are enabled.
2019-11-29T00:17:12.093+0100 7fbcc4c72700 -1 WARNING: all dangerous and experimental features are enabled.
{
"cephfs": {}
}
Updated by Patrick Donnelly over 4 years ago
- Status changed from New to Triaged
- Assignee set to Ramana Raja
- Target version set to v15.0.0
- Source set to Development
- Backport set to nautilus
- Component(FS) MDSMonitor added
Updated by Ramana Raja over 4 years ago
- Status changed from Triaged to In Progress
$ ./bin/ceph osd pool create test 1
$ ./bin/ceph fs add_data_pool a test
$ ./bin/ceph osd pool application get test
{
"cephfs": {
"data": "a"
}
}
`add_data_pool` sets the pool's meta data properly if the pool's application metadata isn't already set/enabled.
In the description, the `osd pool application enable test cephfs` sets the pool's application to `cephfs`. The subsequent `fs add_data_pool` command doesn't update the contents of the pool's application metadata. To get around this for now, you can, execute `osd pool application set test cephfs data a`.
Updated by Patrick Donnelly over 4 years ago
Ramana Raja wrote:
[...]
`add_data_pool` sets the pool's meta data properly if the pool's application metadata isn't already set/enabled.In the description, the `osd pool application enable test cephfs` sets the pool's application to `cephfs`. The subsequent `fs add_data_pool` command doesn't update the contents of the pool's application metadata. To get around this for now, you can, execute `osd pool application set test cephfs data a`.
So if the file system is empty in the "data" field, I would suggest we could overwrite it with the file system name in `add_data_pool`. Makes sense?
Updated by Patrick Donnelly about 4 years ago
- Target version changed from v15.0.0 to v16.0.0
- Backport changed from nautilus to octopus,nautilus
Updated by Greg Farnum about 4 years ago
- Status changed from In Progress to Pending Backport
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #45229: nautilus: ceph fs add_data_pool doesn't set pool metadata properly added
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #45230: octopus: ceph fs add_data_pool doesn't set pool metadata properly added
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".