Recent content by szafran

I've removed pve-manager and then reinstalled it... Now the problem with stalled updates is gone... But the node still doesn't connect to the cluster. Is there any way to fix that, or do I need to reinstall pve from scratch on that node?

Well... I did that on all my 5 nodes... and only one has problems... I doubt it's even remotelly connected to missing dependencies, or more nodes would have been affected.

Hi, Just tried to update (apt update; apt upgrade) and at some point the update process stopped. I've tried rebooting, and running 'dpkg --configure -a' but it can't get any further than to 'Setting up pve-manager (7.3-3) ...' and hangs there. Can someone help me fix that? P.S. Also the node...

Same here. All my 5 nodes are now at 5.18.16-edge and working flawlessly.

Great. And how is the nfs perf for you on this kernel?

5.18.14-edge on both of my pve machines

Edge is ok now. It's been updated and it's working better.

Ok. I think I'll stay with the edge one. But if you'll try the official one please give feedback if it fixed the issue.

Yes.

Not everything is ok on that kernel. From what I've observed the VMs still take ages to reboot/shutdown showing timeouts on sync operations.

After some short test using 5.18.12-edge kernel the nfs shares work much much better now.

Unfortunatelly I'm experiencing the same thing with samba shares. I'll be going with edge kernel now. We'll if that'll help.

I didn't write anywhere that I'm sharing from VM to VM. I'm sharing from host to VM's. That's why I wrote 'same here...' The Ubuntu VMs are the ones giving me most problems. But I suppose that if I used the shared drives as much on other os VMs the effect would be similar. For now... Samba is...

It's a relativelly new proxmox install since I've decided to move my config to proxmox less than 2 weeks ago. But from the start I've had problems with nfs shared disk access from my Ubuntu 20.04 so a few days ago I've installed 22.04 and nothing changed. Now I moved to samba shares instead of...

Same here... root@serwer:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-6 pve-kernel-helper: 7.2-6 pve-kernel-5.15.39-1-pve: 5.15.39-1 pve-kernel-5.15.30-2-pve: 5.15.30-3 ceph-fuse: 15.2.16-pve1...