Recent content by nmmn

mounting manual, same error: mount -t nfs -o vers=4.2 IP:/isos /mnt/pve/ISOS_HDD_CEPH/ mount -t nfs -o vers=4.1 IP:/isos /mnt/pve/ISOS_HDD_CEPH/ mount -t nfs -o vers=4 IP:/isos /mnt/pve/ISOS_HDD_CEPH/ --> mount error: mount.nfs: Protocol not supported

Now i have done an upgrade on 2 Clusters to Proxmox 8 and NFS is working again. (kernel 6.5.11-8-pve) Still have one cluster for Testing.

What does "cat /proc/fs/nfsd/versions" return on NFS server? --> File not existing (Ceph only Support NFSv4) Did you try without vers=4.2 - what did the client/server negotiate? 4, 4.1 and 4.2 are not working Can you boot into old kernel and report working and none versions of kernel...

Error: mount error: mount.nfs: Protocol not supported last version which worked: 5.15.131-2 lsmod | grep -i nfs nfsv4 839680 0 nfs 393216 1 nfsv4 lockd 110592 1 nfs fscache 385024 1 nfs sunrpc 581632 6...

We have nfs Problems with this Kernel: mount.nfs: Protocol not supported NFS v4, 4.1 and 4.2 not working any more... (with our ceph nfs export...)

Hallo Zusammen, wir müssen noch ein paar Proxmox Cluster upgraden. (Proxmox 6.4 to 7 ) Hat das von euch schon jemand mit Linstor DRBD gemacht? Geht das Problemlos? Ist etwas zu beachten? Danke

OK, we had the bug when migrating from EPYC 7543P to EPYC 7543P (same CPU...) but that seems to be NOT gone edit: Problem exist... 6 VMs freezes when we migrate them...

On enterprise we now have installed kernel 5.15.39-4. Proxmox Support told us, that this Kernel fixes the problem.

We have the Problem, when migrating from same CPU to same CPU...

We have same issue with AMD EPYC 7543P Processor... do you have AMD too? Intel is working fine...

Hi, we have same issue with one VM, since the Proxmox Update (7.2) 127: 2022-05-15 16:49:52 ERROR: VM 127 qmp command 'query-pbs-bitmap-info' failed - got timeout 127: 2022-05-15 16:49:52 INFO: aborting backup job 127: 2022-05-15 16:49:55 INFO: resuming VM again 127: 2022-05-15 16:49:55 ERROR...

Hi, we are using DRBD with linstor. After upgrading our testcluster, we get: unsupported type 'drbd'... Now we can't access the storage from the vms. Is anyone using linstor too, and can confirm?

Problem still exists. Anybody any ideas?

Hello, we've a 2-node cluster running privately and went for a 4-node cluster recently. Initial setup went smooth, DRBD and fencing devices are all fine (and working!). Last week we decided to change the vlan for the eth1 interface on all machines simultaneously. E.g. we caused a very, very...