Boot volume on OSD device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Question about OSD sizes: I have two cluster nodes, each with 4x 800GiB SLC SSD using BlueStore. They boot from SATADOM so the OSDs are data-only, but the MLC SATADOM have terrible reliability and the SLC are way overpriced for this application.

Can I carve off 64GiB of from one of the four drives on a node without causing problems? If I understand the strategy properly, this will cause mild extra load on the other three drives as the weight goes down on the partitioned drive, but it probably won’t be a big deal.

Assuming the correct procedure is documented at http://docs.ceph.com/docs/mimic/rados/operations/add-or-rm-osds/, first removing the OSD as documented, zap it, carve off the partition of the freed drive, then adding the remaining space back in.

I’m a little nervous that BlueStore assumes it owns the partition table and will not be happy that a couple of primary partitions have been used. Will this be a problem?

Thanks, Brian
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux