Recent content by yummiweb

Thank you for the suggestion. This might be necessary, as the error is unfortunately still present. The difference seems to be whether the container is running during the backup or not. If the container is off, the backup runs without errors. If the container is running, the described error...

Update: The problem I described (which I observed on several different hosts) has since disappeared. I can't say whether it was fixed by a recent PVE update. If anyone from the team is still reading this: I find it somewhat inconvenient that you can't directly submit discovered bugs as bug...

Addendum: I delved deep into my memory and documentation: For "historical reasons," we need (among other things) a "file-based storage" for VM images and, for example, also for install images. So, we first created a dataset for this, let's call it "Pool/files." Also for "historical reasons,"...

1. You don't need to see things outside this namespace. What I've shown you so far was sufficient: You can see from the provided listing that there are multiple mounts on the ZFS pool, both file-based and (Z)volume-based. 2. You won't find what you're looking for because—as I've already...

Please note that the container is no longer located on the ZVOL: zfs list -ospace,type | grep "ZFS_POOL_A/zvol" ZFS_POOL_A/zvol 444G 389G 0B 96K 0B 389G filesystem ZFS_POOL_A/zvol/subvol-163601-disk-0 12.6G 3.37G 0B...

This is a ZVOL, right? And that is a "normal" Directory Storage on ZFS: What are yor diffrent opinion? Remeber my first Post, please: The problem persist since PVE9, on PVE8 there was no Problem with Backups

This is the configuration at the time of the error (already under PVE9) - both drives on the ZVOL.

The "workaround" unfortunately has a significant drawback: (PVE) snapshots of the container can no longer be created if one of the drives is not located on a ZVOL. Which is also the reason for storing the container on a ZVOL – to create snapshots of the container. What makes the situation...

Proxmox VE 9.1.4 Proxmox Backup Server 4.10 (The problem did not occur under PVE 8 / PBS 3) Object: Container Disk 0: "root" Disk 1: "mp0" (/mnt/db_backups) Disk locations: ZFS ZVOL Problem: Backup to PBS fails with the following error: (Note the double "/" in the path after vzsnap0)...

Bei der Konfiguration eines Filters (extener Dovecot/Sieve) ist mir aufgefallen, dass PMG Status E-Mails nicht erfasst werden. Der Filter sucht im Header nach dem Vorhandensein eines "To:" Eintrages, der bei PMG-eigenen E-Mails aber offenbar nicht vorhanden ist (also als Sender und nicht als...

You're absolutely right, "host" apparently only queries DNS. Ping apparently also resolves locally from files. But: The actual problem has not been solved because, for example, locally running services do not resolve correctly. Specifically, I have a "nut" server running. But it doesn't work...

I would like to have Proxmox resolve its local name itself, without querying an external DNS. A (common) Debian system should actually be able to do this. However, my PVE (a Debian "onTop" installation) doesn't do that. My PVE has (as an example) the following names in the "/etc/hosts" are...

I have noticed that the Debian/Proxmox upgrade "pve7to8" fails at a certain point in my configurations. My PVE is an "on top" installation over a Debian system, as some functions I need are not provided via a native PVE - e.g. LUKS. All preliminary tests by “pve7to8” showed no problems...

This answer is not helpful and ignores all the information and conditions I have given, and it is also completely vague because it does not indicate which IP should be best assigned here? The one from Proxmox? That of a bridge? That of a VM or a container? The problem clearly related to virtual...