Search results

I have been upgrading my customer node by node from 10 gig to 40 gig, now that all nodes are 40 gig I am seeing very very slow ceph. Setup is Dual E5-2690v2 with dual 40 gig bond into a cisco 3132q. OSDs are Samsung 960 EVO 256G NVMe with 2 in each server. Total time run: 92.179118...

You will find that you get a performance boost because of latency even if your not maxing your 10 gig yet...

In fact, I would suggest looking at 40 gig, I just picked up 16 40 gig ethernet cards for $35 each on ebay and a Cisco 3132 40 gig switch for $815.

I am using Proxmox 5.4 with CephFS and multiple file systems. One filesystem is called cephfs and it's on NVMe and the other is cephfs_slow and it's on standard SATA. I can manually mount each file system with: mount -t ceph -o mds_namespace=cephfs virt0,virt4,virt8,virt12:/ /foo mount -t ceph...

So I eventually realized that my problem with /etc/pve, it would lock up accessing files in that tree. I did some searching and found I could fix it by doing the following on ALL nodes: systemctl stop pve-cluster rm -f /var/lib/pve-cluster/.pmxcfs.lockfile I then started pve-cluster one by...

root@virt0:~# fusermount -u /etc/pve fusermount: failed to unmount /etc/pve: Device or resource busy Do I need to reboot? I have VMs I did not want to kill so I have been avoiding that.

root@virt0:~# systemctl restart pve-cluster.service Job for pve-cluster.service failed because the control process exited with error code. See "systemctl status pve-cluster.service" and "journalctl -xe" for details. root@virt0:~# systemctl status pve-cluster.service ● pve-cluster.service - The...

So it was in a good state before the upgrade, now I get: root@virt0:~# pvecm status ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused root@virt0:~# systemctl...

root@virt0:~# systemctl status pve-ha-lrm.service ● pve-ha-lrm.service - PVE Local HA Ressource Manager Daemon Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2018-12-28 14:01:08 EST; 2min 40s ago...

Setting up pve-cluster (5.0-31) ... Job for pve-ha-lrm.service failed because the control process exited with error code. See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details. dpkg: error processing package pve-cluster (--configure): subprocess installed post-installation...