From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Wagner <l.wagner@proxmox.com>
Subject: [pve-devel] applied: [PATCH cluster] pmxcfs: status: create subdirs in /var/lib/rrdcached/db when needed
Date: Fri, 1 Aug 2025 10:50:47 +0200 [thread overview]
Message-ID: <175403824575.2162690.4587419793589930411.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250801083415.64421-1-l.wagner@proxmox.com>
On Fri, 01 Aug 2025 10:34:15 +0200, Lukas Wagner wrote:
> Storage metrics and node metrics use a nested directory structure, e.g.:
> pve-storage-9.0
> somenode
> local
> local-lvm
>
> The second level ('somenode') was not created correctly, leading to
> errors when trying to update the RRD database.
>
> [...]
Applied, thanks!
[1/1] pmxcfs: status: create subdirs in /var/lib/rrdcached/db when needed
commit: 4544b06ec81c82c84cd724e17c803af09e27ae8c
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-01 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 8:34 [pve-devel] " Lukas Wagner
2025-08-01 8:50 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175403824575.2162690.4587419793589930411.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox