Recent content by Sebastian Schubert

Well aparently my colleagues set the write cache to write trough and latency went away and is back at the old levels (around 16:30 the setting was changed, i smoothed the values to 30m so the chart doesnt look like a complete mess).

seems like we already answered this by ourselves in january here: https://forum.proxmox.com/threads/set-write_cache-for-ceph-disks-persistent.103298/ write caching for the disks was wrong

I just made an annotated screenshot of one of the osds (all others osds perform more or less the same) it's a bit more obvious - latency with prox6 was near 0ms.

I've also created a bugzilla bug for this -> https://bugzilla.proxmox.com/show_bug.cgi?id=4297

Hi there, after updating a host from 6.4 to 7.2 today with about 200 containers, none of the containers was bringing up the network. The Network config is done INSIDE the lxc container and NOT via the Proxmox Config (example: net0...

Hi there, i'm about to add a qdevice on a cluster with 2 corosync rings. Does the qdevice have to be reachable on both rings, or whats the best way to have as many redundancy as possible for the qdevice?

HI Fabian, thanks for pointing me to that thread. While the first posts "seem" to go into the direction i'd like to see (prevent creating systems with more that x/y ressources) the last two comments (9+10) seem to go around "enforcing hypervisor(s) to strictly not go over ressoucelimit" which...

Hi there, i was wondering if there are some thaughts about extending the functionality of "pools" (see https://pve.proxmox.com/pve-docs/chapter-pveum.html#pveum_pools) to include Features like "maximum CPU/RAM/DISK Assigned to this pool" when a user tries to add a new VM.

root@an1-kvm01-bt01-b:~# cat /var/log/apt/history.log Start-Date: 2022-04-26 13:01:51 Commandline: apt-get dist-upgrade Install: proxmox-websocket-tunnel:amd64 (0.1.0-1, automatic), libproxmox-rs-perl:amd64 (0.1.0, automatic) Upgrade: udev:amd64 (247.3-6, 247.3-7), proxmox-widget-toolkit:amd64...

In the pop-up Window where the "apt-get dist-upgrade" is running... its hanging for >20 minutes at Processing triggers for pve-ha-manager (3.3-3) ... Meanwhile in the journal we can see that the "trigger for pve-ha-manager" seems to invoke systemd to restart the LRM ... after the last lrm...

Hi there, today i updated some of our clusteres and started the "Upgrade" while still evacuating the VMs off the Host... the dpgk configure for pve-ha-lrm tries to restart .. but gets stuck Apr 26 13:02:37 an1-kvm01-bt01-b pve-ha-lrm[2936243]: Task...

Hi, we changed the write_cache setting for disk based ceph osds by chaging /sys/block/sdXX/queue/write_cache manually. Is there a preffered way to set this in proxmox, or could this even be an enhancement request to set the write cache for ceph disks from pve?

Hi there, trying to update my clusters today (and last week) is a bit frustrating, since every node takes quite a long time to download the packages from the enterprise repository - the ceph repo from download.proxmox.com is way faster ... (Every Server has 1gb/s internet connectivity, we are...

hi, i'll try this when the next bigtwin arrives @ our datacenter - thx for the effort !

OK, i found the issue - i've used ansible to update my system and messed up the repo file: deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise Removed the line with "buster" and it worked as expected ;)