I have a strange problem, if i create a vm with the disk on a smb storage on a truenas machine when i install the vm it creates the disk but then there is an error it can't write to the disk, any ideas?
Proxmox VE 7.3-3 and Truenas 12.0-U8.1
Hi everyone, I transferred a vm from an old installation of pve 6.4-15 to a cluster 7.2-11, the vm has two disks on a smb share and after a while it crashed with the message io error, I tried to change async io on native and now, after 3 hours, it seems to work regularly, I think it is...
My question was about whether it is convenient to activate it in the PBS, which it already compresses, or is it not convenient for performance reasons
Thanks
This is the log of a backup of a vm that has been stopped and restarted and, as you can see, the writing is reduced but the reading is always around 50MiB/s is it not possible to increase the reading speed?
INFO: resuming VM again after 13 seconds
INFO: scsi0: dirty-bitmap status: created new...
I tried and I recreated the empty datastore in the new machine then I copied the data from the old datastore to the new one with rsync and everything reappeared
mmmm... the pbs is in a container so with the host cpu, the client is on a recent hpe server with definitely has aes activated ... I don't think that's the problem
I tried to start two backups simultaneously, of two different VMs, from the same ceph storage and the speed is 50MiB/s for each but 100MiB/s for the total reading of the two processes
It seems to have limits on reading data for each backup ... Is this possible?
This is the bonnie++ benchmark inside a debian container, why I have only 50MiB/s in read with Proxmox Backup Server?
Version 1.98 ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Name:Size etc...
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.