Permissions errors driving me up the wall

bobloadmire

New Member
May 17, 2024
16
1
3
Whenever I run a backup job on Proxmox it fails with my VMs/LXCs at random. I have no idea why. I have changed permissions on all of the folders to 755 recursively, and have checked out the Samba share and made sure the Samba user I'm logged in as has full control of the share recursively. it's driving me nuts. the only issue I can see is that I used Jim's Garage tutuorial and used these commands to also pass through the Samba share to my LXCs from my host:

to mount it on my host:
{ echo '' ; echo '# Mount CIFS share on demand with rwx permissions for use in LXCs ' ; echo '//192.168.0.116/I/ /mnt/lxc_shares/coopnet cifs _netdev,x-systemd.automount,noatime,uid=100000,gid=110000,dir_mode=0770,file_mode=0770,user=xxxxxxxx,pass=xxxxx 0 0' ; } | tee -a /etc/fstab

added group:
groupadd -g 10000 lxc_shares

add mount point to lxc:
{ echo 'mp0: /mnt/lxc_shares/coopnet/,mp=/mnt/coopnet' ; } | tee -a /etc/pve/lxc/LXC_ID.conf

error log attached.

but typical error looks like:

Code:
INFO: creating vzdump archive '/mnt/lxc_shares/coopnet/PVEstorage/dump/vzdump-lxc-102-2024_06_22-02_02_01.tar.zst'
INFO: Total bytes written: 7475978240 (7.0GiB, 158MiB/s)
INFO: zstd: /*stdout*\: Permission denied
ERROR: Backup of VM 102 failed - command 'set -o pipefail && 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=/var/tmp/vzdumptmp224476_102' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/var/tmp/vzdumptmp224476_102' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' . | zstd '--threads=1' >/mnt/lxc_shares/coopnet/PVEstorage/dump/vzdump-lxc-102-2024_06_22-02_02_01.tar.dat' failed: exit code 1
INFO: Failed at 2024-06-22 02:03:39
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp224476_103 for temporary files

or

Code:
INFO: Starting Backup of VM 106 (lxc)
INFO: Backup started at 2024-06-22 02:05:54
INFO: status = running
INFO: CT Name: prowlarr
INFO: including mount point rootfs ('/') in backup
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: prowlarr
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/5100/root/ to /var/tmp/vzdumptmp224476_106
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.Y.pl.IWMi6J" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#200H\#303d\#003`/.NA.pl.9q2ytr" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#001/.T,pl.a4YdWi" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/.36.0/unicore/lib/GCB/.Y.pl.rBGgnZ" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.Allowed.ph.OYyKuK" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.Recommen.pl.nyXQlL" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/.36.0/unicore/lib/NFDQC/.14_0.pl.jCshV5" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.15_0.pl.ie3h7e" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/.36.0/unicore/lib/NFDQC/.10_0.pl.l77GuQ" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.12_1.pl.g9NWbR" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/.36.0/unicore/lib/NFDQC/.13_0.pl.8qbl7n" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.3[0.pl.Wc7YZH" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.5_0.pl.fUg9E6" failed: No such file or directory (2)
ERROR: rsync: [receiver] mkstemp "/var/tmp/vzdumptmp224476_106/\#260\#013\#260d\#003`/.Right.pl.G7IpoN" failed: No such file or directory (2)
ERROR: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]
ERROR: Backup of VM 106 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/5100/root//./ /var/tmp/vzdumptmp224476_106' failed: exit code 23
INFO: Failed at 2024-06-22 02:06:02
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp224476_107 for temporary files


full log attached.
 

Attachments

  • task-pve-vzdump-2024-06-22T09_00_00Z.log
    28.1 KB · Views: 0
Last edited:
@fweber you asked me to tag in my post. When i get this error, about 10% of the time my host goes all grey/? and I have to restart the service to get the interface back to normal.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!