Search results

I have two nodes in a cluster which mount Ceph over the network, but that mounting is broken and I cannot remount as /etc/ceph/ does not have the symlink in it and the keyring file. A third node that is roughly configured the same was in the same state until it was rebooted. Ceph itself is ran...

That is irrelevant, there is _zero_ Windows involved. My desktop isn't Windows, it's Linux, same for the nextCloud server (Linux). I uploaded via the webGUI, which is my browser. Where do you think Windows comes into play at all here? Because there's zero Windows involved.

There is zero Windows anything involved. I don't know why you think there is.

I honestly cannot explain how the slash changed between the stat command, and my first comment. I would not have intentionally changed that slash.

root@REDACTED:/var/log/proxmox-backup/tasks/E3# stat 'UPID:REDACTED:000289CB:3BEF2DE3:000003B1:64B24022:backup:REDACTED\x3act-182:root@pam:' File: UPID:REDACTED:000289CB:3BEF2DE3:000003B1:64B24022:backup:REDACTED\x3act-182:root@pam: Size: 455331 Blocks: 896 IO Block: 4096...

Local computer in particular example is/was Ubuntu 23.10. I keep meaning to do the stat thing but have not yet, that's on my end, sorry! I need to do that.

1. No other operating system has direct access to these disks to any capacity. The storage that PBS uses is local to the OS. 2. The observed naming with slash is observed for multiple backup files, this is not a one-off. 3. nextCloud in no way has mangled the filenames. The involvement was...

Sounds like whatever is resulting in that outcome is probably resulting in the same thing on my end too. And yeah it looks like you're also speaking to my original concern that the invalid slash characters should have been blocked before file creation (and I'm not even sure why Proxmox Backup...

Being able to see the IP addresses in lists of VMs/CTs on each node, across the cluster, and being able to "search" for which object has an IP address (assuming Proxmox even "knows") would all be VERY useful. Especially at-scale. I'm currently working with a new-to-me client and learning plenty...

I have total confidence that these files were created by PBS, all evidence in-hand shows it. And the scenario you describe has not happened for this relevant PBS system.

I don't know exactly when I will be able to get back onto that system next, but I will try my darndest to remember. As for the error... "Could not create path" since it interprets the slash in the file as referencing "wanting" to make a folder.

Oh I'm with you about upgrading that system, but to be clear this system isn't "mine" but one that I have provided support for. So I will be convincing about upgrades likely in the near future, but "how soon" is probably not "soon". The underlying filesystem for the Datastore is btrfs (not set...

Yeah in both Proxmox VE and Proxmox Backup Server, we really need the ability to see higher-level statistics for usage. Some examples: How much Bytes-On-Disk was used total for each Backup Task across an entire Proxmox VE cluster (one backup task configuration typically backs things up across...

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?