Recent content by Christian St.

Of cause it is easier concerning scalability to use switches in the corosync link. (In all links) But in the end with a mesh network there will be always a scalability problem. If you want to add nodes you will also need a storrage connection.. It is just a question of what you have planned. If...

Where is the recomandation to seperate ceph cluster and ceph public network? Proxmox says, "as an optional step you can go even further and separate the OSD replication & heartbeat traffic as well. This will relieve the public network and could lead to significant performance improvements...

This is, what the Wiki says (https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster): Public Network: You should setup a dedicated network for Ceph, this setting is required. Separating your Ceph traffic is highly recommended, because it could lead to troubles with other latency...

This file is on your local machine, so no one of us can see it.

This is the structure proxmox recomands: The most essential part in a Proxmox HA Cluster is the Corosync link. Corosync should have minimum 1 (better 2) seperate physical link (not shared with any other traffic) because of latency. Corosync links do not need a high bandwidth connection, but a...

This should describe the way: https://forum.proxmox.com/threads/migrate-a-kvm-image-to-proxmox-ceph.23112/

Can you mark this thread as solved, as your problem and the problem of Derelict could be solved with Alwins help?

Can you check timedatectl status In the shell of all nodes?

Time syncronization works with ntp https://pve.proxmox.com/wiki/Time_Synchronization Maybe this is helpful,otherwise you should search in the forum concerning time and ntp. Could it be, that the Port 123 is blocked via a firewall?

Can you please check what your configuration concerning osd_pool_default_min_size and osd_pool_default_size is? You can find this under Node > Ceph > Configuration > and there under [global] I do not really understand why there is a degreded pg, when there is just one osd missing. Normally it...

There should be one. It is the one which is down and out. Look at the OSD tabs on the nodes. There should be one with the status down and out. You should try to bring it up and in again. Clock skew, as written comes from an problem with the time syncronization. Mayby looking in the forum after...

Is the time on all nodes syncronized?

What is the status of the 27th osd?

I do not know, if this is in any relation. Does this happens long time after your problems started, while ceph was recovering? I had written a comment in another thread some days ago, where I found somthing concerning the nf_conntrack: Check nf_conntrack: This connection tracking and limiting...

Do you have access via the GUI to the Tab Shell, or is this resticted?