No, you shouldn't invoke it that way, you should just not specify a WAL device at all if you want it to be stored with the DB - if not otherwise specified the WAL is automatically stored with the other metadata on the DB device. You should do something like:
ceph-volume lvm prepare --bluestore --data /dev/sdc --block.db /dev/sda1 Rich On 09/04/18 09:19, Hervé Ballans wrote: > Hi, > > Just a little question regarding this operation : > > [root@osdhost osd]# ceph-volume lvm prepare --bluestore --data /dev/sdc > --block.wal /dev/sda2 --block.db /dev/sda1 > > On a previous post, I understood that if both wal and db are stored on the > same separate device, then we could use a single partition for both...which > means we could do : > > # ceph-volume lvm prepare --bluestore --data /dev/sdc --block.wal /dev/sda1 > --block.db /dev/sda1 > > and so on with other uniq wal/db partition for other OSD... > > Did I get that correctly ? > > Thanks, > > Hervé > > > Le 07/04/2018 à 17:59, Gary Verhulp a écrit : >> >> I’m trying to create bluestore osds with separate --block.wal --block.db >> devices on a write intensive SSD >> >> I’ve split the SSD (/dev/sda) into two partditions sda1 and sda2 for db and >> wal >> >> >> >> I seems to me the osd uuid is getting changed and I’m only able to start the >> last OSD >> >> Do I need to create a new partition or logical volume on the SSD for each >> OSD? >> >> I’m sure this is a simple fail in my understanding of how it is supposed to >> be provisioned. >> >> Any advice would be appreciated. >> >> Thanks, >> >> Gary
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
