Recent content by Chriswiss

Same thing for me.

Thank you for the fast service!

Great, thanks, that's fine, it works with TARGET.

Hello, Yesterday I made the following upgrades: 2020-07-13 07:31:31 upgrade libavfilter7:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1 2020-07-13 07:31:31 upgrade libswscale5:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1 2020-07-13 07:31:31 upgrade libavformat58:amd64 7:4.1.4-1~deb10u1...

You can if you want to update only the : - pve-kernel-5.4.44-2-pve - pve-kernel-5.4 - pve-kernel-helper

You can try the kernel 5.4.44-2 which seems for me stable since yesterday.

I couldn't wait to try this new kernel. :) For the moment reboot the node and it works fine on 5.4.44-2!

Sorry I misspoke. ;) I didn't try 5.4.44-2. I stay on 5.4.41 because it's a production machine and I can't migrate all VMs to another node for testing.

Unfortunately the problem is presented on a production machine. I stay for the moment on the 5.4.41 I hope that others can try.

In any case, thank you for your prompt attention. ;)

TOSHIBA KXG50ZNV512G Filesystem : Only ZFS

For me two NVME disks : cat /sys/block/nvme0n1/queue/scheduler [none] mq-deadline cat /sys/block/nvme1n1/queue/scheduler [none] mq-deadline

Same problem here with 5.4.44 on only one machine of the cluster. It's a machine in production, I can't really touch it. I booted on 5.4.41 with no problem. - On this machine SMB and NFS are activated. - On the others that work with 5.4.44 just NFS is enabled. CG

Hmm, yes, it is possible. I need to look this way. Thanks :)

Thank you for your answer. I just need it to get a better look and block unauthorized connections. CG