Recent content by rahman

OK, but the verify jobs are read-only jobs, they don't create any snapshot etc, so why does it prevent creation of a snapshot an only one but all? As you can see in the attached job logs, the sync job does its job for the other snapshots without any problem, even the Verify job was still...

Hi, Is it normal to get bellow error in a Sync (pull) job when also a Verify job running on the same datastore? 2026-05-16T09:00:14+03:00: [vm/164]: sync group vm/164 failed - 2026-05-15T22:00:43Z: while creating locked snapshot 'BackupDir { store: "default", ns: BackupNamespace { inner...

Thanks, I will give it a try. Someone should already merge it then :D

Hi, When using "qmrestore" for backup restore tests it uses 4 threads by default: "using up to 4 threads .... fetching up to 16 chunks in parallel". So how can I configure these values? I want to decrease it for testing (to see if it will affect S3 problems I am having). "man qmrestore" does...

Hi, It seems there is some calculation error in GC job status modal: As you can see in this screen shot it shows duration as +10 hours. But the jobs logs and the summary page shows the real duration correctly as ~2 hours: 2026-04-30T00:00:00+03:00: starting garbage collection on store...

Sure, here it is: root@pbs1:~# apt-cache policy proxmox-backup-server proxmox-backup-server: Installed: 4.1.7-2 Candidate: 4.1.7-2 Version table: *** 4.1.7-2 500 500 http://download.proxmox.com/debian/pbs trixie/pbs-no-subscription amd64 Packages 100 /var/lib/dpkg/status...

It seems this fixed the problem, thanks :) I could not find any meaningful result for this error on Google search. Everything seems to working now. root@pbs1:~# hexdump /var/lib/proxmox-backup/s3-statistics/ulakfkm-default-bucket-ulakfkm.shmem | head -n 1 0000000 6ee0 fc58 4d1a 05b4 0000 0000...

Here it is: root@pbs1:~# hexdump /var/lib/proxmox-backup/s3-statistics/ulakfkm-default-bucket-ulakfkm.shmem | head -n 1 0000000 0000 0000 0000 0000 0000 0000 0000 0000

Last sync job from local datastore to s3 backed datastore failed with a strange error: detected wrong types in mmaped files: incorrect magic number for request counters detected I see the same error in all PBS GUI sections about this datastore. How can I check what is the problem...

Another snapshot that failed: 2026-04-18T14:33:54+03:00: verify ulakfkm:vm/147/2026-04-12T04:03:34Z 2026-04-18T14:33:54+03:00: check qemu-server.conf.blob 2026-04-18T14:33:54+03:00: check drive-scsi1.img.fidx 2026-04-18T23:37:37+03:00: verified 1929315.07/2029084.00 MiB in 32622.67...

Hi, still having same issues with verification jobs. I tried removing rate limiting for S3 endpoint in PBS S3 endpoint settings, did not make any difference. Added static mapping to /etc/hosts file for S3 endpoint IP address, did not worked either. So is there a way to make PBS S3 client more...

2026-04-01T16:11:38+03:00: verify ulakfkm:vm/206/2026-03-03T18:01:12Z 2026-04-01T16:11:38+03:00: check qemu-server.conf.blob 2026-04-01T16:11:38+03:00: check drive-scsi0.img.fidx 2026-04-01T16:32:48+03:00: verified 23359.43/50996.00 MiB in 1270.29 seconds, speed 18.39/40.15 MiB/s (0...

As verify takes so long, GC and sync jobs runs once a day while verify also running. Can't know if it causes this. But I checked sync and GC jobs for "2026-03-30T12:23:48+03:00" to "2026-03-30T13:39:36+03:00" which is vm/183 verify errored, and there is was no gc or sync jobs running between...

root@pbs1:~# proxmox-backup-manager version --verbose proxmox-backup 4.0.0 running kernel: 6.17.13-2-pve proxmox-backup-server 4.1.5-2 running version: 4.1.4 proxmox-kernel-helper 9.0.4 proxmox-kernel-6.17 6.17.13-2...

Hi, I have a Ceph Backed S3 datastore that is synced from local datastore. I am running weekly verify jobs. The problem is last job complains about validation errors but when I look content of datastore on PBS GUI it does not match: Job ID: v-35b45b04-d2ac Datastore: ulakfkm Verification...