Actions
Bug #62593
openceph-bluestore-tool bluefs-bdev-new-db creates block.db symlink to non-persistent /dev/dm-## instead of given and stable /dev/VG_NMAE/LV_NAME path
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
I added a dedicated DB device to an existing OSD and then found the auto-created symlink for block.db to not point to the device path as I gave it.
The DB device in my case is actually a LV on a VG "ceph-journal" with a flash device as its PV. This is to allow for multiple OSD to use a single SSD, quite a common approach I believe.
1) So I created a LV via:
lvcreate -L 200G --name block.db-osd1 ceph-journal
2) I then shutdown the OSD and migrated the DB to the new device / LV:
systemctl stop ceph-osd@1.service ceph-bluestore-tool bluefs-bdev-new-db --path /var/lib/ceph/osd/ceph-1 --dev-target /dev/ceph-journal/block.db-osd1
When looking at /var/lib/ceph/osd/ceph-1
I saw that the new block.db
symlink pointed to /dev/dm-53
.
This of course is not stable across reboots.
Actions