Re: [ceph-users] Fwd: Separate --block.wal --block.db bluestore not working as expected.

On 4/7/18 4:21 PM, Alfredo Deza wrote: On Sat, Apr 7, 2018 at 11:59 AM, Gary Verhulp wrote: 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

Re: [ceph-users] Fwd: Separate --block.wal --block.db bluestore not working as expected.

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

Re: [ceph-users] Fwd: Separate --block.wal --block.db bluestore not working as expected.

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

Re: [ceph-users] Fwd: Separate --block.wal --block.db bluestore not working as expected.

On Sat, Apr 7, 2018 at 11:59 AM, Gary Verhulp wrote: > > > > > > 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 > > > > > >

[ceph-users] Fwd: Separate --block.wal --block.db bluestore not working as expected.

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