Search results

root@redacted:~# proxmox-backup-manager versions --verbose proxmox-backup unknown running kernel: 6.1.2-1-pve proxmox-backup-server 2.4.6-1 running version: 2.4.3 pve-kernel-helper 7.3-8 pve-kernel-6.1...

I copied the name of the file exactly (except changing two sensitive words to redacted, which did not alter any slash characters at all in the process). So yes, I am 100% confident the slash is as I have shown above. That is what was in the filename both before and after the redaction. There...

I've recently had a need to copy off a PBS system the Task History Logs and a bunch of those Task History files have been created with "bad" naming conventions. This has caused me problems for syncing the files onto my nextCloud, and I'm sure you'll see the problem with this example...

OOO "Renowned Member" :3

Due to some intricacies of reverse-proxy stuff (which I'm really not going to go into for security reasons), I have added an entry to the /etc/hosts file for every node in a particular Proxmox VE cluster. This is so that the FQDN of the SMTP server I am sending notifications through resolves to...

I find that Proxmox RAM reporting is never accurate, and it's quite useless to be honest. I build a new VM and haven't done anything with it. 6GB RAM capacity, only using about 400MB, and qemu-guest-agent installed (Ubuntu 20.04 in this case) and it reports over 5GB of RAM used. And that 400MB...

Oh wait, I won't be able to do backup comments without the Proxmox Backup Server?

hahah oops! Sorry! XD

Can we get the ability to add comments to a backup we create? I'd really like it if I could add something like "Before installing game server files" or whatever. Even if the backup gets deleted in backup cycling, that can be super handy. Please? :)

And how exactly is that command going to work if I don't already know the PID? I have a very large amount of PIDs in that /proc folder...

Do you really want me to run my system to 0% swap and 0% RAM to prove this is a problem? Because I'm not going to do that. Both of the problematic systems have continued to use more and more swap each day, one of which is at 50% swap usage. The evidence I've presented is conclusive enough to...

Thanks to my alerting failing to E-Mail me (unrelated issue) I have been able to observe multiple nodes continue to follow this growth pattern without stopping. The swap grows every time a backup happens, there is nothing else going on, and this happens every day (as my backups are daily) once...

My issue isn't inherently with the caching, it is with swapping. Swapping on these nodes doesn't happen until the RAM is full (with cache and application data, etc). This is why I flush the cache, as it "buys more time" before swapping occurs. If this caching happened without any swapping, I...

Alright, so I want to clarify, I can totally appreciate the scepticism around what I'm saying here. I agree that it is not quite matching expectations. I run a cluster where two of the nodes exhibit this behaviour, and one doesn't. I've tried to find an explanation, and that's part of why I'm...

Swap exists on disk. This is the case whether it is Linux or Windows. Just because you think there is no problem, doesn't mean there is no problem. I've explained this enough to you, and you have not provided any help or solution here. I'm done explaining. I've explained this more than enough...

The swap usage is unnecessary in this scenario, and the cause of it is the backup task. The swap usage causes unnecessary disk usage that I would rather have allocated for other tasks. That's the issue. The backup task is not releasing the cache and it continues to build up until it goes into...

Well I'm trying to convey what I'm seeing here, if you don't believe me that's on you. I've spent a very large amount of time trying to identify the cause of this situation and the only consistent aspect is the backups and that the cache is not getting freed up and is pushing into swap. You say...

I'm not against stuff being put into cache, the issue is the cache never gets cleared, or reduced, after a backup task. And that's what I'm trying to address here, as it is the root cause. I don't want to turn off swap because it's meant to be there for emergency purposes, not day to day...

I disagree in this particular case, primarily because the perpetually growing cache pushes data into swap. And you may not see why I care about that, but it increases disk usage in ways that are completely unnecessary and avoidable, plus offer no benefit. Day to day the VMs running on the host...

Uh the cache never gets freed up. That's the problem. Before the backup task the cache does not grow, and it does not get released between backup tasks. Nothing goes into swap until the cache uses all the remaining RAM. I would be okay with the cache growing if it actually reclaimed or freed...