Hi,
When you ran the ceph-volume command, did you do it within the
container of the OSD? Running it with the container of the OSD
would make sense as to why I was getting the errors I was getting.
yes, I ran the commands within the OSD container. Don't forget to run
the "migrate" command as well after you created a new db.
Just one more remark about your followup question in the initial post:
Followup question: if I do seem to have to go the route of
destroying the OSD and
re-creating it with the flags for point the DB/WAL to the SSD
partition, the syntax I have
seen is this:
ceph-volume lvm prepare --bluestore --block.db --block.wal --data
VOLUME_GROUP/LOGICAL_VOLUME
Beside the fact that you assume correctly and the command lacks the
db/wal device specification, I strongly recommend to let cephadm
handle the entire process of OSD creation, just ensure you have a
fitting spec file. Don't prepare any LVs manually beforehand, except
for such a case as right now where you want to move DBs out of the
main device. But if you want to create OSDs from scratch, use the
orchestrator, it does all of the work. And don't forget the --dry-run
flag if you want to apply a new spec (ceph orch apply -i osd-spec.yaml
--dry-run).
Regards,
Eugen
Zitat von Alan Murrell <Alan@xxxxxxxx>:
Hello,
I ran the commands from the "regular" cephadm shell ('cephadm shell
--') but did not specify an OSD (I wasn't aware you could do that)
When you ran the ceph-volume command, did you do it within the
container of the OSD? Running it with the container of the OSD
would make sense as to why I was getting the errors I was getting.
I can give it a try and let you know how it goes, and if necessary
go from there.
Sent from my mobile device. Please excuse brevity and ttpos.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
