I doubt this matters, but it might. These drives were formatted with ceph-disk, not ceph-vol. They are, however, mounted in the right place, and the block device is linked to the correct partition.
SystemD has been ignoring enable/disable instructions for a while, I don't know why. I assume new detection code.
/etc/ceph/ceph.conf
mon host = 192.168.120.1 192.168.120.2 192.168.120.3
ceph mon dump: 16T23:16: 32.234657- 0500 08T10:30: 10.123758- 0500 168.120. 1:3300/ 0,v1:192. 168.120. 1:6789/ 0] mon.temple-h1 168.120. 2:3300/ 0,v1:192. 168.120. 2:6789/ 0] mon.temple-h2 168.120. 3:3300/ 0,v1:192. 168.120. 3:6789/ 0] mon.temple-h3
epoch 7
fsid <redacted>
last_changed 2020-05-
created 2016-04-
min_mon_release 15 (octopus)
0: [v2:192.
1: [v2:192.
2: [v2:192.
netstat -ltup |grep ceph-mon:
tcp 0 0 temple-h1:3300 0.0.0.0:* LISTEN 1722/ceph-mon
tcp 0 0 temple-h1:6789 0.0.0.0:* LISTEN 1722/ceph-mon
I doubt this matters, but it might. These drives were formatted with ceph-disk, not ceph-vol. They are, however, mounted in the right place, and the block device is linked to the correct partition.
SystemD has been ignoring enable/disable instructions for a while, I don't know why. I assume new detection code.