On a recent Luminous cluster, with nvme*n1 devices, the class is
automatically set as "nvme" on "Intel SSD DC P3520 Series" :
~# ceph osd tree
ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF
-1 2.15996 root default
-9 0.71999 roo
On Wed, Aug 1, 2018 at 4:33 AM, Jake Grimmett wrote:
> Dear All,
>
> Not sure if this is a bug, but when I add Intel Optane 900P drives,
> their device class is automatically set to SSD rather than NVME.
Not sure if we can't really tell apart SSDs from NVMe devices, but you
can use the --crush-de
Hi,
Can you benchmark your Optane 900P with `fio -fsync=1 -direct=1 -bs=4k
-rw=randwrite -runtime=60`?
It's really interesting to see how much iops it will provide for ceph :)
--
With best regards,
Vitaliy Filippov
___
ceph-users mailing list
ceph
Am 1. August 2018 10:33:26 MESZ schrieb Jake Grimmett :
>Dear All,
Hello Jake,
>
>Not sure if this is a bug, but when I add Intel Optane 900P drives,
>their device class is automatically set to SSD rather than NVME.
>
AFAIK ceph actually difference only between hdd and ssd. Nvme would be hand
Dear All,
Not sure if this is a bug, but when I add Intel Optane 900P drives,
their device class is automatically set to SSD rather than NVME.
This happens under Mimic 13.2.0 and 13.2.1
[root@ceph2 ~]# ceph-volume lvm prepare --bluestore --data /dev/nvme0n1
(SNIP see http://p.ip.fi/eopR for out
