cannot unlink file for /mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.tmp/qemu-server.conf: Permission denied at /usr/share/perl5/PVE/VZDum

[tomdeb]

Hi,

proxmox noob and trying to backup my VM's to a truenas zfs pool which I have added to the datacenter as a SMB share

can anyone help me figure this 1 out, is this due to permissions?

the smb share is a zfs pool that was created on truenas, which i have virtualised in proxmox

my vm storage is on a seperate nvme drive, am backing these upto the truenas smb share

all 3 vm's get to 100% and then fail

INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2022-03-10 18:55:45
INFO: status = runningINFO: VM Name: dockerINFO: include disk 'scsi0' 'vm:vm-102-disk-0' 40G
INFO: backup mode: snapshotINFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.vma.zst'
INFO: issuing guest-agent 'fs-freeze' commandINFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '9cea7e38-f6a0-44b8-9149-f86b5b1e7807'INFO: resuming VM again
INFO: 5% (2.1 GiB of 40.0 GiB) in 3s, read: 721.4 MiB/s, write: 240.1 MiB/s
INFO: 7% (2.9 GiB of 40.0 GiB) in 6s, read: 277.9 MiB/s, write: 252.0 MiB/s
INFO: 18% (7.5 GiB of 40.0 GiB) in 9s, read: 1.5 GiB/s, write: 174.3 MiB/s
INFO: 20% (8.2 GiB of 40.0 GiB) in 12s, read: 232.0 MiB/s, write: 223.1 MiB/s
INFO: 22% (8.9 GiB of 40.0 GiB) in 15s, read: 223.5 MiB/s, write: 223.5 MiB/s
INFO: 23% (9.5 GiB of 40.0 GiB) in 18s, read: 236.8 MiB/s, write: 229.6 MiB/s
INFO: 25% (10.3 GiB of 40.0 GiB) in 21s, read: 252.5 MiB/s, write: 250.1 MiB/s
INFO: 27% (10.9 GiB of 40.0 GiB) in 24s, read: 227.2 MiB/s, write: 226.9 MiB/s
INFO: 29% (11.6 GiB of 40.0 GiB) in 27s, read: 232.0 MiB/s, write: 223.4 MiB/s
INFO: 30% (12.3 GiB of 40.0 GiB) in 30s, read: 226.0 MiB/s, write: 220.8 MiB/s
INFO: 32% (13.0 GiB of 40.0 GiB) in 33s, read: 230.8 MiB/s, write: 230.0 MiB/s
INFO: 34% (13.7 GiB of 40.0 GiB) in 36s, read: 234.4 MiB/s, write: 227.0 MiB/s
INFO: 35% (14.4 GiB of 40.0 GiB) in 39s, read: 238.0 MiB/s, write: 237.8 MiB/s
INFO: 37% (15.0 GiB of 40.0 GiB) in 42s, read: 209.0 MiB/s, write: 203.9 MiB/s
INFO: 39% (15.6 GiB of 40.0 GiB) in 45s, read: 232.0 MiB/s, write: 223.7 MiB/s
INFO: 40% (16.3 GiB of 40.0 GiB) in 48s, read: 233.2 MiB/s, write: 230.1 MiB/s
INFO: 45% (18.2 GiB of 40.0 GiB) in 51s, read: 625.9 MiB/s, write: 215.2 MiB/s
INFO: 49% (20.0 GiB of 40.0 GiB) in 54s, read: 622.3 MiB/s, write: 247.8 MiB/s
INFO: 72% (29.2 GiB of 40.0 GiB) in 57s, read: 3.1 GiB/s, write: 82.5 MiB/s
INFO: 100% (40.0 GiB of 40.0 GiB) in 1m, read: 3.6 GiB/s, write: 2.7 KiB/s
INFO: backup is sparse: 27.81 GiB (69%) total zero data
INFO: transferred 40.00 GiB in 60 seconds (682.7 MiB/s)
cannot unlink file for /mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.tmp/qemu-server.conf:
Permission denied at /usr/share/perl5/PVE/VZDump.pm line 1075.
cannot restore permissions to 0100755 for /mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.tmp/qemu-server.conf:
at /usr/share/perl5/PVE/VZDump.pm line 1075.cannot remove
directory for
/mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.tmp:
Permission denied at /usr/share/perl5/PVE/VZDump.pm line 1075.ERROR:
Backup of VM 102 failed - unable to rename
'/mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.vma.dat' to
'/mnt/pve/backups/dump/vzdump-qemu-102-2022_03_10-18_55_45.vma.zst'INFO: Failed at 2022-03-10 18:56:46INFO: Backup job finished with errorsTASK ERROR: job errors

 

[fabian]

yes it's due to permissions seems like creating the temporary .dat file works, but renaming, changing permissions, and removing files fails.

 

[tomdeb]

unless i am stupid permissions seem to all be correctly set

 

[fabian]

can you try touching a test file as root from the PVE host?

 

[notKakarot]

Facing this same error while trying to mount s3 bucket and doing a backup on it. I just updated the role permission for all S3 action. Will update here if it succeeds this time.

UPDATE: I can touch a file as root from the PVE host just fine. But the error still exists. Something else I tried was renaming the file manually since that was the error. And this was the error:

mv: cannot move 'vzdump-qemu-101-2024_02_16-15_10_09.vma.dat' to 'vzdump-qemu-101-2024_02_16-15_10_09.vma.zst': Function not implemented

UPDATE 2: I got it working by downloading from the s3 bucket and renaming it with `zst` extension (instead of .dat). It now shows up in proxmox under the disk -> Backup.