Recent content by brad_mssw

After quite a bit of testing, setting ms_crc_header = true but leaving auth_client_required = none auth_cluster_required = none auth_service_required = none cephx_sign_messages = false cephx_require_signatures = false ms_crc_data = false and my problem goes away.

I should also mention I have ms_crc_data = false ms_crc_header = false in my ceph.conf relating to disabling crcs

I guess this is libceph in the kernel, I can reproduce it by: mount.ceph ceph1,ceph2,ceph3:/ /mnt/isos Looking at the kernel source code, I *should* be able to turn it off (and should by default by reading the config files)...

I'm trying to use cephfs for isos. Prior to proxmox v6, we just created a mount point with /etc/fstab: none /mnt/isos fuse.ceph _netdev,defaults 0 0 That worked (and still does). Now I noticed PVE6 has a cephfs option, so in trying to do that, I receive a timeout when trying to add the...

@oldfart please start a different thread for your issue which has nothing to do with the issue in this thread

Looks like the corosync crash should be fixed from this PR: https://github.com/kronosnet/kronosnet/pull/257 And is now part of pvetest ... anyone experiencing the corosync crash, please try it! Direct link here if not on pvetest...

@ahovda ah interesting, we had major issues with OpenVSwitch and finally switched away from it once PVE started supporting vlan-aware native linux bridges (and of course after we figured out how to use them properly, had some issues breaking out vlan interfaces for the host). Anyhow, once we...

@Jema have you upgraded to the latest libknet and also tried the suggestion from @ahovda: ? @ahovda your cluster still stable now?

our new cluster will be running mellanox connect-x4 as well, except 2x50Gbps ... so its good to know that mellanox seems good for a long time.

@NoahD that is a 7001 series processor, @andy77 is asking about 7002 series ... I too am curious, we just had a new HW order approved with 7402P processors and are still on 5.4 since we're tracking the corosync crash bug before we upgrade to v6.

@David Herselman do you think the corosync crashes are also related to bnx2?

@astnwt you may want to add it to https://bugzilla.proxmox.com/show_bug.cgi?id=2326 I know we are waiting to upgrade to PVE 6 until we see a resolution on this as I haven't seen anyone state that a certain combination of hardware of configuration has been determined to cause this.

I would at least recommend compiling and installing the latest official intel ixgbe driver and seeing if it magically resolves your issue. If so, maybe the proxmox guys can either bundle the newer version, or maybe switch to a newer kernel that already bundles a newer driver...

You know what they say about assumptions ... evidence in my case showed different behavior from different driver versions in the kernel.

This may also be related: https://forum.proxmox.com/threads/sfp-optic-not-working-anymore.43493/