Search results

Yes/No. It all depends on the workload and resource usage of other services. So in short, you will need to test it.

Schau mal in den Thread rein. ;) Dort ist auch das Paper aus 2018 verlinkt. https://forum.proxmox.com/threads/proxmox-ve-ceph-benchmark-2020-09-hyper-converged-with-nvme.76516/ Ansonsten kann ich noch unsere und Ceph's docku empfehlen. https://pve.proxmox.com/pve-docs/chapter-pveceph.html...

Because of this. And if you know what you are doing, then you don't need to ask. ;)

Can you please post a pveversion -v? And please stick with the debian intalled version. That's also the one which we test on.

Wieso? Nix mehr mit'm Verstand oder hast es gelöst? ;) :p

LVM-thin is used on a local disk not the Synology. While I suppose to understand where you are going with this, I do not recommend it.

Yes, AFAIK. See the first comment. https://bugzilla.proxmox.com/show_bug.cgi?id=1282#c1 Best see the shutdown policy. https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#_node_maintenance

But LVM-thin is not shared. It's a local storage. And before you ask, it shouldn't be used on iSCSI. It makes it possible when a second node writes onto such storage it will overwrite data. This is because of the thin provisioning.

The bandwidth isn't so important for corosync, 1 GbE is enough. The factor is latency, corosync needs low and stable latency to provide accurate information about the state of the cluster. Well, adapters are such a case. :cool: But it will quite definitely reduce the performance. Why not...

Yes, this is correct. With that said, you may be able to do snapshots on the Synology side. But Proxmox VE won't be aware about them. https://www.synology.com/en-global/dsm/feature/snapshot_replication

Please post the current /etc/pve/storage.cfg.

Is the x-vga set? https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_pci_passthrough_vm_config

Look at the storage types in the link. iSCSI doesn't support snapshots from the Proxmox VE side. And Synology doesn't run ZFS. https://pve.proxmox.com/pve-docs/chapter-pvesm.html

It depends on your setup. If corosync is on a separated NIC port not sharing traffic and there are multiple links, then it should be no problem. Besides it will always show that corosync has an offline member. If this node isn't needed on the cluster, why not just remove it completely? In a...

Well, you will need to use VMs.

Depends on the workload, but in principle it works. The only downside you won't be able to achieve reliable HA. Since that requires extra NIC ports. https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_ha_manager Well, manual setup can be done. But it still has the same issue with HA...

Add more network cards! Otherwise don't use HA.

Can you try kernel 5.4.78-2? And what's in the kernel log (dmesg)?

Never run corosync on shared links [1]. With that said, at least one link needs to be on a separate NIC port. The additional links [1] may be shared, but preferably not. This is especially important if HA [2] is used. [1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_pvecm [2]...

How much downtime is acceptable? And do you need the NFS server at all (eg. all linux clients)?