Search results

I've been chatting with support to bug hunt a little bit; the default is "no rate limit" fwiw

Just out of curiosity, do you know what the default "put-rate-limit" is? I couldn't find it in the docs yet.

I'm not sure this is possible. If I'm not mistaken when a backup is pruned, not only is the name/timestamp/etc lost, but also the map of which chunks go where on disk. Garbage collection just takes chunks that are unreferenced by a backup and removes them. You really need that "backup" So in...

For those curious, I had overlapping IP addressing in one of my cluster IPSets. I would have had no idea what to look at, but shanreich found the issue. If anyone else runs into this same issue, I suggest running through your IPSets looking for overlaps

So for whatever reason, the forums are telling me I'm not allowed to send DMs to you. Am I doing something wrong? shanreich got in touch via DM and I got the log file to them

Hello, I'm working on trying out the new nftables proxmox-firewall on a couple nodes of our dev cluster to see how it works and I hit something I can't quite work past. Our rules are kind of a mess on our dev cluster, so it's probably going to be a good test of how the new code works. Issues...

@fiona , can you confirm if this package is now in the subscription repo? I'm looking and I see 6.8.8-2 on both a production (support) servers and one of our lab servers (community) when I run `apt changelog proxmox-kernel-6.8`, and I see 6.8.8-2 available. So I think it's available now, but I...

Rebooting the nodes got the new microcode into the Kernel. Or at least it seems to have... Unfortunately it's looking like hot-patching CPUs isn't supported in Proxmox-VE. The Proxmox-VE kernel is compiled without CONFIG_MICROCODE_LATE_LOADING. The short version is that microcode can be...

See also this proxmox wiki page: https://pve.proxmox.com/wiki/Storage:_LVM_Thin

What "pvdisplay" shows is a physical volumes and doesn't show whether or not you're using volume thin provisioning. What does "lvdisplay" show? This will show if you're using lvm thin provisioning or not

I haven't, I got busy with other tasks and I also figured "time may fix it". We have a shiny new proxmox cluster I might be able to try things out on (that will have support on it). I'll report what happens, though it may be a few weeks in the future.

I determined that it wasn't necessary to set this value. Most people use LVM thin provisioning. To quote @fabian, If you do use LVM thin provisioning, you can always edit /etc/lvm/lvm.conf to insert this line: issue_discards = 1

I'll give it a try, but these are AMD CPUs

I'm having a weird issue getting the firmware loaded onto a system and I'm not sure if it's related or not. I installed all updates on proxmox-ve 8.0.2 (pve-no-subscription repo), rebooted and I'm still seeing some warnings in my logs. root@pve2:~# journalctl -k --grep=microcode Aug 14...

For completeness, a fresh install from the 6.4-1 ISO (which installed the proxmox-ve:6.3-1 package) had issue_discards set to 1. root@pve-test:~# lvmconfig --typeconfig full | grep issue_discards issue_discards=1 root@pve-test:~# grep issue_discards /etc/lvm/lvm.conf #...

Ah that makes sense. Thanks for clarifying @fabian Not relevant to this forum but kind of curious as to why Debian doesn't default this to on.

You know... When I installed 7.4 (from proxmox-ve_7.4-1.iso), the defaults are to set issue_discards to 0 as well. This system was originally a 5.x install and I've done several upgrades so I'm wondering if it was a setting from a long time ago. I don't believe it's anything I tuned myself.

I had a chance to do a fresh Proxmox-VE install (inside a VM if that makes any difference). The defaults are to leave issue_discards set to 0 (off). The install was using proxmox-ve-8.0-2.iso. root@pve-test:~# lvmconfig --typeconfig full | grep issue_discards issue_discards=0...

I absolutely got the prompt and selected the package maintainer's version following the wiki instructions: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Upgrade_the_system_to_Debian_Bookworm_and_Proxmox_VE_8.0

Hi, I'm not sure if this is an "issue" per-say, but I noticed that during an upgrade the `issue_discards = 1` config line is removed from lvm.conf and the new default is `issue_discards = 0`. I also could not find the setting anywhere else in /etc/lvm, for example in lvmlocal.conf. Is this an...