Search results

Most of it is is post #3. Longer version below: Jan 26 01:03:41 pbs proxmox-backup-proxy[6187]: starting new backup on datastore 'BKP_PBS_NCP': "vm/131/2021-01-26T00:03:41Z" Jan 26 01:03:41 pbs proxmox-backup-proxy[6187]: download 'index.json.blob' from previous backup. Jan 26 01:03:41 pbs...

There is this error for several VM. Jan 26 00:30:11 pbs proxmox-backup-proxy[6187]: error during snapshot file listing: 'unable to load blob '"/mnt/BKP/vm/168/2021-01-25T23:30:03Z/index.json.blob"' - No such file or directory (os error 2)' Jan 26 00:30:13 pbs proxmox-backup-proxy[6187]: error...

There's a 400 error (bad request) in PBS'syslog: Jan 26 01:04:18 pbs proxmox-backup-proxy[6187]: Upload statistics for 'drive-scsi0.img.fidx' Jan 26 01:04:18 pbs proxmox-backup-proxy[6187]: UUID: 517ba5ee62f74948b3f5f12cde84d5b5 Jan 26 01:04:18 pbs proxmox-backup-proxy[6187]: Checksum...

Hi. I got this in my mailbox this morning, last night backup; if the mail is right, one of the VM did not backup correctly. 137: 2021-01-26 01:03:23 INFO: Starting Backup of VM 137 (qemu) 137: 2021-01-26 01:03:23 INFO: status = running 137: 2021-01-26 01:03:23 INFO: VM Name: lm-old 137...

Great. Can you modify the thread and add "Solved" to the subject?

It seems you have declared the backup datastore at the root of your PBS server. You should delare it in an empty subfolder of the server. See here: https://forum.proxmox.com/threads/permission-issue-error-on-garbage-collection.79014/

You were right. I found my error: I used this repo to create a VM (the day the GC failed) instead of the correct storage. I'm removing the "Disk image" property of the storage right now!

Hi Fabian, this should not have changed (no server reboot, no new user, no known change). Also, backup happens correctly, pruning too. root@pbs:/mnt# ls -la total 36 drwxr-xr-x 4 root root 4096 Oct 19 15:33 . drwxr-xr-x 18 root root 4096 Jan 18 16:00 .. drwxrwxrwx 14 backup backup...

.gs-status file still exist in the root of the mountpoint (my repo is NFS). File date is the end of the last GC that worked correctly...

Hi. Since two days (january 15), garbage collect start at midnight. Before that, it started during the day, at very different time (see screenshot). Since this schedule change, it fails with this error: Garbage collection failed: cannot continue garbage-collection safely, permission denied...

I had the "Directory not empty (os error 39)" error on my NFS datastore. The error was shown on backup pruning (trying to delete backups older than the retention). Upgrading to 1.0.6-1 seems to have fixed it. I upgraded yesterday then forced a "Datastore prune" and it went OK. No more error in...

root@pve01:~# ceph osd pool autoscale-status POOL SIZE TARGET SIZE RATE RAW CAPACITY RATIO TARGET RATIO EFFECTIVE RATIO BIAS PG_NUM NEW PG_NUM AUTOSCALE SSD 6005G 3.0 71535G 0.2519 1.0...

Hi all. I might hit this (what RokaKen) says about the difference between the suggested number of PG (I have 40 OSD, I previously setup 1024 PG with Nautilus) and what pg_autoscale thinks/wants (it says there's too many placement group after Octopus upgrade). I don't intend to enable the...

The bug seems to link the issue to sata/ide (vs scsi), but the error in syslog are related to NIC aren't they?

Same issue here, I have only one template and its backup fails. The backup of a VM that is a linked clone of the template is OK. pve-qemu-kvm: 5.1.0-6 qemu-server: 6.2-19 On first try yesterday: 164: 2020-11-15 18:46:51 INFO: Starting Backup of VM 164 (qemu) 164: 2020-11-15 18:46:51 INFO...

It seems this fixed the issue, backup is working when launched from PVE GUI. A new dirty-bitmap is created for each VM. Is it because I rebooted the nodes (post-upgrade) or because I moved the VM (to reboot the nodes)?

Same issue here since yesterday (this night backup did not happen). What changed: yesterday I upgraded my PBS to 0.9-4 and my PVE nodes to 6.2-15.

Seems fixed in 0.9-4 BETA (at least, after the upgrade, I can browse the datastore).

Great you know what it the issue. Is there a bug ID to follow?

Dominik, how can I get the api response? If you're talking about the response to this call "GET https://serverIP:8007/api2/json/nodes/localhost/tasks?running=1&limit=100", then the response payload is: {"data":[],"total":0} If it's the response to "GET...