Well it's getting faster..
If you want to try with mitigations off you have to add this to
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet mitigations=off"
then run #update-grub
I thought the big speed difference affected only older CPUS though?
Definitely try RAID 10. Also, about the CPU, that's the problem with some of the new CPUS. Their single thread rating is sometimes not that much better. Sure a little better than these aging servers but not a big boost. They are more for multi core and PCIE lanes, but if your app is single...
First of all thank you. I had to remove the: auto eno1 then restarted networking and it worked
Then I re-installed ifupdown2 got into gui reset the settings and it made it how it was originally but it now works with the auto eno1 lines. Is this because ifupdown2 was removed on the upgrade?
Is there a way to stop the logs in
/var/log/syslog
/var/log/proxmox/api/auth.log
To be constantly written with root@pam allowed every 10 second without using api tokens?
Thank You
Merci pour les fotos!
Yes, I think mine was similar. Except the Path's (Chemin) depending on if you want to give less permission you can point to /datastore/backup and different Role's but then you have to test make sure everything works.
Also if you have an existing datastore we have to...
I just spent hours playing with this... All to remove one annoying log entry....
The token thing is very confusing.
The only way I was able to get it to work was have a user
admin@pbs
as well as an admin@pbs!client1 (token)
But in the datastore permissions I had to add BOTH the user...
Any luck did you try longer?
EDIT: I see your other thread you had to resort to mounting read only and cloning... Glad you got it to work
https://forum.proxmox.com/threads/how-to-recover-failed-raid-access-storage.51105/#post-426671
Can you keep it running? may take longer - this sort of thing makes me re-evaluate zfs honestly. Slow Hard disks? or does it just get slower with even more TB... When this happened to me it made me re-evaluate zfs in production but it only took about 20-30 minutes for me 2TB. But even after...
This thread contiues to have a variety of results based on the newer kernel, meaning that there is / was an issue with the current kernel. However I am still not sold on proxmox 7.0... 6.4 is rock solid so I am going to continue to wait. I don't feel the entire professional/enterprise...
So does this io_uring have higher standards for more consistent memory etc? where as prior to this you could get by with lesser hardware?
Do I just 'hope' my hardware will work if I use this new feature? Do I upgrade to 7...hope it wont crash if it crashes then disable io_uring?
This is...
Ok I am glad you are trying though, it helps perhaps agree that it is more hardware related. I have a production 6.4 that is flawless and concerned about upgrading to 7.0. I don't see a rush at moment.
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.