ct-Backup fehlgeschlagen -- warum?

Dec 19, 2012
509
16
83
Hallo.
Wir haben einen Container, von dem leider kein Backup angefertigt werden kann. Die Meldung lautet:

Code:
INFO: starting new backup job: vzdump 114 --storage Diskstation --remove 0 --mode snapshot --node pve --compress zstd
INFO: Starting Backup of VM 114 (lxc)
INFO: Backup started at 2021-08-16 10:00:57
INFO: status = running
INFO: CT Name: i-do-it
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
INFO: creating vzdump archive '/mnt/pve/Diskstation/dump/vzdump-lxc-114-2021_08_16-10_00_57.tar.zst'
INFO: tar: /mnt/pve/Diskstation/dump/vzdump-lxc-114-2021_08_16-10_00_57.tmp: Cannot open: Permission denied
INFO: tar: Error is not recoverable: exiting now
INFO: cleanup temporary 'vzdump' snapshot
ERROR: Backup of VM 114 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/mnt/pve/DS-Cevex/dump/vzdump-lxc-114-2021_08_16-10_00_57.tmp' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd --rsyncable '--threads=1' >/mnt/pve/DS-Cevex/dump/vzdump-lxc-114-2021_08_16-10_00_57.tar.dat' failed: exit code 2
INFO: Failed at 2021-08-16 10:00:58
INFO: Backup job finished with errors
TASK ERROR: job errors

Alle anderen Backups funktionieren problemlos (gleiches Storage).
Das Verzeichnis besitzt diese Rechte:
Code:
drwxrwxrwx 3 root root       20480 Aug 16 10:00  dump


Woran kann das liegen?
 
Last edited:
Können Sie bitte den Folgende posten:
  • pveversion -v
  • cat /etc/vzdump.com
  • cat /etc/pve/storage.cfg
  • cat /etc/pve/lxc/114.conf
 
Klar, kein Problem:
pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.124-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-5 pve-kernel-helper: 6.4-5 pve-kernel-5.4.128-1-pve: 5.4.128-1 pve-kernel-5.4.124-1-pve: 5.4.124-2 pve-kernel-5.4.119-1-pve: 5.4.119-1 pve-kernel-5.4.114-1-pve: 5.4.114-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.2-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.1.0 libproxmox-backup-qemu0: 1.1.0-1 libpve-access-control: 6.4-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.4-3 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.2-3 libpve-storage-perl: 6.4-1 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.1.12-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.6-1 pve-cluster: 6.4-1 pve-container: 3.3-6 pve-docs: 6.4-2 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-4 pve-firmware: 3.2-4 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-6 pve-xtermjs: 4.7.0-3 pve-zsync: 2.2 qemu-server: 6.4-2 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.5-pve1~bpo10+1

cat /etc/vzdump.conf # vzdump default settings #tmpdir: DIR #dumpdir: DIR #storage: STORAGE_ID #mode: snapshot|suspend|stop #bwlimit: KBPS #ionice: PRI #lockwait: MINUTES #stopwait: MINUTES #size: MB #stdexcludes: BOOLEAN #mailto: ADDRESSLIST #maxfiles: N #script: FILENAME #exclude-path: PATHLIST #pigz: N

cat /etc/pve/storage.cfg nfs: Diskstation export /volume1/backups path /mnt/pve/Diskstation server 192.168.1.7 content backup prune-backups keep-last=2

cat /etc/pve/lxc/114.conf arch: amd64 cores: 2 hostname: idoit memory: 2048 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=6A:31:AF:D6:DC:D5,ip=dhcp,type=veth ostype: ubuntu rootfs: zfs-pool-2:subvol-114-disk-0,size=15G swap: 1024 unprivileged: 1