Hi
I run PBS inside an LXC, that LXC ran out of space, though that was quickly fixed, actual storage is a passed through ZFS Pool via directory mountpoint on Proxmox Host.
Due to that my backup job did not seem to run successful, on Proxmox I got the notification for error in backup job with the following problem:
While that is not really critical, the webui does not seem to load the metadata for these backups, therefore I also can't really restore them.
Is there a job to regenerate such metdata?
GC Job did not solve it.
When I try to verify it, I get this error:
What's my best bet now?
Just ignore these backups and they will hopefully be self-cleanup up after retention period, restart these tasks somehow?
I run PBS inside an LXC, that LXC ran out of space, though that was quickly fixed, actual storage is a passed through ZFS Pool via directory mountpoint on Proxmox Host.
Due to that my backup job did not seem to run successful, on Proxmox I got the notification for error in backup job with the following problem:
Code:
Logs
====
vzdump --storage pbs-ssd-pool --mailnotification always --mode snapshot --mailto XXXXXXX --notification-mode notification-system --all 1 --notes-template '{{guestname}}' --fleecing 0 --quiet 1
102: 2025-07-02 04:00:00 INFO: Starting Backup of VM 102 (lxc)
102: 2025-07-02 04:00:00 INFO: status = running
102: 2025-07-02 04:00:00 INFO: CT Name: bookstack
102: 2025-07-02 04:00:00 INFO: including mount point rootfs ('/') in backup
102: 2025-07-02 04:00:00 INFO: backup mode: snapshot
102: 2025-07-02 04:00:00 INFO: ionice priority: 7
102: 2025-07-02 04:00:00 INFO: create storage snapshot 'vzdump'
102: 2025-07-02 04:00:01 INFO: creating Proxmox Backup Server archive 'ct/102/2025-07-02T02:00:00Z'
102: 2025-07-02 04:00:01 INFO: set max number of entries in memory for file-based backups to 1048576
102: 2025-07-02 04:00:01 INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp3811538_102/etc/vzdump/pct.conf fw.conf:/var/tmp/vzdumptmp3811538_102/etc/vzdump/pct.fw root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 102 --backup-time 1751421600 --entries-max 1048576 --repository root@pam@10.10.20.22:ssd-pool
102: 2025-07-02 04:00:01 INFO: Starting backup: ct/102/2025-07-02T02:00:00Z
102: 2025-07-02 04:00:01 INFO: Client name: lenovo1
102: 2025-07-02 04:00:01 INFO: Starting backup protocol: Wed Jul 2 04:00:01 2025
102: 2025-07-02 04:00:01 INFO: Error: mkstemp "/var/log/proxmox-backup/tasks/A3/UPID:pbs:000000CA:00001DA3:000006E6:686492A1:backup:ssd\\x2dpool\\x3act-102:root@pam:.tmp_XXXXXX" failed: ENOSPC: No space left on device
102: 2025-07-02 04:00:01 INFO: cleanup temporary 'vzdump' snapshot
102: 2025-07-02 04:00:01 ERROR: Backup of VM 102 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp3811538_102/etc/vzdump/pct.conf fw.conf:/var/tmp/vzdumptmp3811538_102/etc/vzdump/pct.fw root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 102 --backup-time 1751421600 --entries-max 1048576 --repository root@pam@10.10.20.22:ssd-pool' failed: exit code 255While that is not really critical, the webui does not seem to load the metadata for these backups, therefore I also can't really restore them.
Is there a job to regenerate such metdata? GC Job did not solve it.
When I try to verify it, I get this error:
Code:
2025-07-02T06:56:31+02:00: verify ssd-pool:ct/102/2025-07-02T02:00:00Z - manifest load error: unable to load blob '"/ssd-pool/ct/102/2025-07-02T02:00:00Z/index.json.blob"' - No such file or directory (os error 2)
2025-07-02T06:56:31+02:00: Failed to verify the following snapshots/groups:
2025-07-02T06:56:31+02:00: ct/102/2025-07-02T02:00:00Z
2025-07-02T06:56:31+02:00: TASK ERROR: verification failed - please check the log for detailsWhat's my best bet now?
Just ignore these backups and they will hopefully be self-cleanup up after retention period, restart these tasks somehow?
