Stale File Handle when running a backup

Boss

New Member
Apr 22, 2024
24
0
1
Running PVE 8.1.3
Getting a strange error when running individual backups (not scheduled).

Some VMs reports a Stale file handle when the backup process runs
Code:
INFO: starting new backup job: vzdump 118 --mailnotification always --notes-template '{{guestname}}' --all 0 --node sv-pve-03 --compress zstd --mode suspend --prune-backups 'keep-last=1' --storage NAS-X-01
INFO: Starting Backup of VM 118 (qemu)
INFO: Backup started at 2024-06-26 19:39:44
INFO: status = running
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: VM Name: vm-itop-01
INFO: include disk 'scsi0' 'local-lvm:vm-118-disk-0' 32G
INFO: suspending guest
INFO: creating vzdump archive '/mnt/pve/NAS-X-01/dump/vzdump-qemu-118-2024_06_26-19_39_44.vma.zst'
ERROR: unable to open file '/mnt/pve/NAS-X-01/dump/vzdump-qemu-118-2024_06_26-19_39_44.vma.dat' - Stale file handle
INFO: aborting backup job
INFO: resuming VM again after 1 seconds
INFO: resume vm
ERROR: Backup of VM 118 failed - unable to open file '/mnt/pve/NAS-X-01/dump/vzdump-qemu-118-2024_06_26-19_39_44.vma.dat' - Stale file handle
INFO: Failed at 2024-06-26 19:39:48
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors

When I deleted the storage device (NAS-X-01) and readded it a few of the failed backups were then re-run successfully, but there are a few still that keep reporting the same problem.
There is no mount point defined in fstab, but it is defined in /proc/mounts on each node

Code:
//172.16.17.147/PVE /mnt/pve/NAS-X-01 cifs rw,relatime,vers=3.1.1,cache=strict,username=backup,uid=0,noforceuid,gid=0,noforcegid,addr=172.16.17.147,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1 0 0

All my scheduled backups (to another device, configured exactly the same) work as expected daily.

Looking at /mnt/pve/NAS-X-01 from the PVE servers, I can see all the completed backups from each node. The only file remaining from the failed backups is a .log file. It appears that it can't create the .dat file?

Update: I've now managed to backup all the VMs except for 2 which still both report the Stale File Handle error - and despite multiple attempts now, these two fail every time I attempt a backup.
It's obviously not a permissions problem as all the other VMs backed up OK to this device.
 
Last edited:

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!