Backup fails "unable to create temporary directory"

S

stiffler

New Member
Jul 21, 2023
5
0
1
Hello,

I have set two backup jobs in proxmox, for a long time now and they worked fine; the backup is being made on a NAS. However, it suddenly stopped working. I have not modified anything in proxmox, nor the NAS (no updates, no nothing):

1.JPG
i checked the "dump" folder and it is strange that it appears it has nobody and nogroup permissions; maybe it was like that since forever, i don't know, just checked it now while trying to tshoot. And no, i cannot manually create a folder inside "dump" due to lack of privileges.
2.jpg

The vzdump file looks like this (again, not touched, unmodified):
3.jpg

It is very strange how it worked for so many months and suddenly wothout any modification, a privileges problem appears.

Please, advice what can i tshoot next.

Thx
 
Hi,
since you state that you did not change anything, first thing to check would be if you ran out of storage space. Also check if you can create a file on the NFS share by e.g. touch /mnt/pve/Datastore_NFS/dump/test.tmp.

stiffler said:
a privileges problem appears.
Click to expand...
This issue is not necessarily related to a permission problem.
 
Chris said:
Hi,
since you state that you did not change anything, first thing to check would be if you ran out of storage space. Also check if you can create a file on the NFS share by e.g. touch /mnt/pve/Datastore_NFS/dump/test.tmp.


This issue is not necessarily related to a permission problem.
Click to expand...
Hi, thx for the reply. No, i cannot create anything inside "dump" (folder or file, nothing):
Code: 
root@robhst1:~# touch /mnt/pve/Datastore_NFS/dump/test.tmp
touch: cannot touch '/mnt/pve/Datastore_NFS/dump/test.tmp': Permission denied
root@robhst1:~#

first thing to check would be if you ran out of storage space
Click to expand...
On the NAS, where is the target of the backup? there is enough space, yes.
 
stiffler said:
touch: cannot touch '/mnt/pve/Datastore_NFS/dump/test.tmp': Permission denied
Click to expand...
Okay, but then something did change, because you will not suddenly loose permissions. Double check the permissions on the NFS side and post the output of mount. Did you lately reboot or remount the NFS share?
 
Chris said:
Okay, but then something did change, because you will not suddenly loose permissions. Double check the permissions on the NFS side and post the output of mount. Did you lately reboot or remount the NFS share?
Click to expand...
I did not remount the NFS share in the Proxmox device. Since i first mounted this NFS share (don't know...one year aprox maybe), both the proxmox and the NFS device got rebooted and restarted many times along this time.
the NAS device where the NFS share is located, is a True Nas system; its NFS is set to a preset ACL called "open", which is not restricted.

output of command mount:

Code: 
root@robhst1:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=32767364k,nr_inodes=8191841,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6560408k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22920)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ZFS01 on /ZFS01 type zfs (rw,xattr,noacl)
ZFS01/Data01 on /zfsdata type zfs (rw,xattr,noacl)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
172.34.34.3:/mnt/StoragePool/DataStore_NFS on /mnt/pve/Datastore_NFS type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.34.34.2,local_lock=none,addr=172.34.34.3)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=6560404k,nr_inodes=1640101,mode=700,inode64)
root@robhst1:~#
 
Smells like a problem on the TrueNAS side. You should also test to mount the NFS share on some other machine to check if the same problem surfaces. Sorry but I don't know anything about TrueNAS to help you more.
 
AmateurProgrammer said:
Sorry but I don't know anything about TrueNAS to help you more.
Click to expand...

No pb AmateurProgrammer, i had a look at it. ANd indeed, it was a problem on the TrueNAS. I mentioned above the NFS share had an ACL applied to it, called "open" which means it is the least restrictive, allowing access to all; so although that ACL was applied since ages, it appears that out of the sudden (although appearing as applied) it was not working anymore. So i re-applied it and now it is working again. Mistery.
Thanks for the help.
this thread may be closed.
 
You must log in or register to reply here.
Top Bottom