Thank you for your reply, so If I understand right, In our case we can Proxmox self let be on the Crucial MX500, as long as we host the VM's on the Intel SSDs as mentioned above, so we shouldn't have a high IO delay which causes downtime if we host the VMS on these Intel Drives in a new ZFS...
Dear,
Currently we have some troubles with High IO delay on almost any 'heavy' write on the VM. Our Proxmox is currently installed on Crucial MX500 with ZFS RAID 1. I was searching on the web and I saw that this could happen because of these disks can't handle much IOPS for VM Hosting.
I was...
Hello,
Currently we running 2x MX500 2TB ZFS RAID 1 which are consumer SSD's, my question is if I add two additional Samsung datacenter grade SSD's which are the PM883 with RAID 1 ZFS, can I still let proxmox run on the consumer SSD's when I run all the VM's on the two ssd grade ssds?
Thanks...
Goodevening,
I have a question according to my Proxmox setup, I have a 128GB RAM server with 2X 2TB SSD's in RAID1 (ZFS) configured. I saw that the wear out is around 10% in 34 days, I was researching on the internet and find a possible solution to adjust the ZFS settings like:
recordsize to...
Dear,
I installed proxmox on a dedicated server with 128Gb RAM. After a couple days a saw that my RAM was filled over 60% (almost 70%) with only 3 VMS each 4GB. Therefore I was searching on the internet and read that ZFS uses 'free' RAM to cache. I was wondering if this is a static behaviour...
Thank you for your reply. The Issue is fixed, the cause of this Issue was a NFS storage which was not mounted correctly. So the pvestatd service throw back the communication error. Only weird thing is that I wasn't be able to see the current DISK space on the local disks, so somehow the...
The difference is that the local storage is a folder on the filesystem and the local-lvm is a volume. If Proxmox is installed on ZFS then it doesn't matter that much where to store the vm images. So it depends on the installation.
Dear,
I've created an cluster with two nodes. The problem seems to be on one node, currently there are running VM's on the local storage, but if I want to create an new VM he can't find the local storage during an communication failure / timeout (0) / connection timed out (596). I see the stats...
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.