after trying several kernels I figured out that em28xx also breaks everything, after blacklisting the module everything works fine again.
have you considered blacklisting the module?
absolutely, this is just the local copy, I am using a NAS for backups.
But you're right - if I keep them on the NAS and would set a refreservation on the ROOT vol the issue should be resolved.
Hi everyone,
due to the default setup the root volume can become filled with backups and the whole system halts. What would be the best way to prevent this? Is it possible to reserve space for the root vol but not it's subvolumes?
Speaking of which..: https://forum.proxmox.com/threads/compile-proxmox-ve-with-patched-intel-iommu-driver-to-remove-rmrr-check.36374/post-346136
@proxmox-staff: how about integrating this patch into the kernel, switched off by default. I think it will help many people achieving higher IO and...
Hi Dunuin,
I have the one NVMe SSD as a system drive and for the VM images. No RAID. ashift=13, partition alignment is fine.
NAME PROPERTY VALUE SOURCE
rpool volblocksize - -
rpool/ROOT volblocksize - -...
root@pve2:~# pveperf
CPU BOGOMIPS: 76799.52
REGEX/SECOND: 4762554
HD SIZE: 441.71 GB (rpool/ROOT/pve-1)
FSYNCS/SECOND: 1008.93
So I installed proxmox on a new server, looking at the speeds of the fio-benchmark the NVMe drive seems to perform quite well:
formated as ext4...
adapted for ZFS root partition, as grub rescue might not see the ZFS root: (e.g. compression algorithm not found..)
don’t reboot after setup (checkbox before install starts), then abort setup
zpool import -R /mnt rpool -d /dev/disk/by-id/…-part3
plug in boot usb-stick
format usb with msdos...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.