Am 26.07.25 um 03:06 schrieb Aaron Lauterer: > This patch series does a few things. It expands the RRD format for nodes and > VMs. For all types (nodes, VMs, storage) we adjust the aggregation to align > them with the way they are done on the Backup Server. Therefore, we have new > RRD defitions for all 3 types.
applied series with a bunch of follow-ups from Lukas (thanks!) and myself, thanks! > KNOWN ISSUES: > * on a live system, renaming the source RRD files to FILE.old doesn't seem to > work as expected and besides the renamed ones, new ones without the .old > prefix > show up again. I suspect some interaction with rrdached and/or pmxcfs > receiving > new data. FWIW, while I prepared a service to handle this on-boot, delaying that by more than a one or two minutes is not ideal either, and while we could differentiate between smaller and bigger setups (thus less or more time required for the migration), it is probably simpler just doing it on the upgrade itself, albeit getting this synchronized would be good too, maybe playing around with stopping rrdcached before the upgrade might help, or make pmxcfs not commit anything if it sees a flag file or the like, but it's only a short period of time of RRD metrics, nothing critical, so I did not want to block this on that. btw. It would be still very important to add a short section for this to the upgrade guide, mentioning how one can continue the upgrade again later, not all will see the message in the d/postinst output. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
