Search results

I encountered a similar issue while restoring an LXC container and wanted to share what I found to be the root cause and solution. The error "No space left on device (os error 28)" during the restore process is typically caused by insufficient disk space allocated to the container. When...

Alright, everything is working fine... I've been using namespaces recently, and I simply forgot to add the namespace in PBS before adding the PBS resource to the PVE host. After creating the namespace "pve-ovh," everything started working. I only noticed this when I was preparing the...

The permissions are "rather" fine because the resource is mounted with the same permissions for both PVE 6.4 and PVE 7.4. It works fine on 6.4, but there is a 400 error on 7.4.

and the same resource (backup-pbs) for 6.4-13

I have the same issue "400 - error listing snapshots". The problem occurs when I want to mount a resource to the PVE host from a virtual PBS machine that is running on that host. I would like to have the ability to restore backups. pve-manager/7.4-3/9002ab8a proxmox-backup-server: 2.3.1-1...

I have the same issue "400 - error listing snapshots". The problem occurs when I want to mount a resource to the PVE host from a virtual PBS machine that is running on that host. I would like to have the ability to restore backups. pve-manager/7.4-3/9002ab8a proxmox-backup-server: 2.3.1-1...

yes, what you say would be correct for e.g. ext4, but at the time of not freeing up space the file system on PBS was ZFS Ok I'm back, just with an update After changing the file system to ext4 for PBS, fortunately the space freed up. It's a little strange that no one observes such a case.

Unfortunately, changing the file system for the datastore did not help. You may not see it clearly, but there is a trend that "local-zfs" on the pve1 host will grow relative to "backup" Now there is such a configuration: PROD-PBS Probably when I return in a while local-zfs will grow until...

Unfortunately that's not it, that's what I checked in the first place. I'll just add that PVE1 as well as PBS use ZFS as the file system. As a test I added another disk to PBS, but this time I made an ext4 file system on it, I'll check in a moment if it frees up space.

Hello, Does anyone know how to solve the problem of not freeing up space in ZFS? I have two physical machines: pve1 and pve2 On pve1, as you can see, there is a PROD-PBS machine that has a disk resource allocated from pve1 (practically all of it for PBS) The "backup" resource is linked for...

But using the settings in datacenter, it is impossible to limit the speed during "live migration". I just tested this and it only worked when I set "migrate_speed" directly in the vm configuration. pve-manager/7.3-3/c3928077 (running kernel: 5.15.74-1-pve)

On freebsd with version 4.2 still does not work unfortunately. I tested once on OviOS and there this functionality works. link: ovios

Hello :) Is there any way to note in the pve-firewall logs what action (DROP/REJECT/ACCEPT) was taken when it happens on "security groups"? firewall for example: GROUP-default_rules-OUT 04/Apr/2022:10:33:53 +0200 IN=fwbr100i0 OUT=fwbr100i0 PHYSIN=tap100i0 PHYSOUT=fwln100i0...

thank you very much :-) it works as i wanted.

Hello, I searched the forums, but couldn't find it. Well, after doing a PCI passthrough to a VM, I cannot recover the network cards back to the host after shutting down the VM that had the cards connected via PCI passthrough. I have tried by echo 1 > /sys/bus/pci/devices/0000:82:00.0/remove...

pvecm e 1

as far as I know, after executing this command apt-get update --allow-releaseinfo-change you will be on the old-stable branch and will be able to update Debian to old-stable (10) and proxmox 6.x https://forum.proxmox.com/threads/proxmox-ve-support-lifecycle.35755/ in the InRelease file, the...

If I am not mistaken then: apt-get update --allow-releaseinfo-change will only explicitly change information from stable to old-stable. If you don't want to upgrade your cluster to debian 11 and therefore proxmox 7, with this command you will stick to the old-stable version that has support for...

for qcow2 format it should be possible to store a persistent bitmap as it says here: https://qemu-project.gitlab.io/qemu/interop/bitmaps.html#bitmap-persistence

According to the qcow2 documentation, it is possible to obtain a persistent dirty bitmap for the qcow2 disk format. so shyly i ask if there are any plans for persistent dirty bitmap for qcow2 format in proxmox?