I have on all Servers PVE 8.2.2 with Kernel 6.8.4
- Genoa 9374F, Asus rs520a-e12-rs12u
- Genoa 9374F, Asus rs520a-e12-rs12u
- Ryzen 7 5800X, X570D4I-2T
- i3-1315U, NUC 13
- i3-1115G4, NUC 11
- 2x E5-2637 v3, HPE ML350 G9
- Xeon Silver 4210R, HPE DL360 G10
- Xeon Silver 4210R, HPE DL360 G10
- 2x E5-2620 v3, DL360 G9
- E3-1275 v5, FUJITSU D3417-B2
No issues at all, no crashes, all run as Perfect as they can.
Since its unknown what the issue is, that may be helpfull!
None has less uptime as 4 days, some have 14days+, and the longest uptime is 22 days.
Because 22 days ago i started to move to the 6.8.4 kernel and a kernel switch needs sadly a reboot xD
I dont remember when the kernel was released, but i bet it was 22 days ago available in the test repo already.
Cheers
I waked today morning up and an Centos 7 VM with Kernel 6.8.8 from elrepo frozen up.
The task that made the VM "Freeze", was a backup job inside the VM.
The VM mounts over Samba a Folder from my Backup-Server:
//172.88.8.84/Nachtsicherung /mnt1/backup cifs credentials=/etc/fstab-bsmount.txt,iocharset=utf8,vers=3.0 0 0
The 172.88.8.84 Backup-Server is a PVE 8.2.2 Server with 6.8.4 Kernel, i just run Samba Server natively on it.
The Storage is ZFS on the Backup-Server.
The Script that started to run inside the VM, started exactly at 0 Oclock, exactly when the VM froze up. It simply compresses some folders via gzip directly to the /mnt1/backup folder, so samba destination (Backup-Server)
Now this is either a Samba issue why the VM frooze, or it's an ZFS issue on the Backup-Server.
I think its actually both tbh.
I run an far too new kernel on Centos 7 (6.8.8) and the Samba Package is pretty old (Samba v. 4.10.16)
However, i have sadly no logs, because there arent any errors. Im still searching tho.
But this error/freeze is not really related to Proxmox in my opinion, however, didnt had any crashes before, i changed now some things, and if i find sth out, i will report.
Cheers
PS: Only the VM frooze.
No crashes on any Proxmox Server.