Error backing up VM to SMB share, but LXC's back up sucessfully

[ClandestineAvacado]

I have a USB hard drive (on a Raspberry Pi) shared out via Samba and added as storage in Proxmox. I am able to back up (and restore) LXC's to/from this device, but when I run a backup on the only VM I have, it fails with the below output.

Any ideas how to troubleshoot this?

2024-01-11 15:45:45 INFO: Starting Backup of VM 500 (qemu)
2024-01-11 15:45:45 INFO: status = running
2024-01-11 15:45:45 INFO: backup mode: stop
2024-01-11 15:45:45 INFO: ionice priority: 7
2024-01-11 15:45:45 INFO: VM Name: pve-ubuntu-s
2024-01-11 15:45:45 INFO: include disk 'scsi0' 'local-lvm:vm-500-disk-0' 32G
2024-01-11 15:45:45 INFO: stopping virtual guest
2024-01-11 15:45:54 INFO: restarting vm
2024-01-11 15:45:57 INFO: guest is online again after 12 seconds
2024-01-11 15:45:57 ERROR: Backup of VM 500 failed - unable to open '/mnt/pve/smb-public/dump/vzdump-qemu-500-2024_01_11-15_45_45.tmp/qemu-server.conf' - Stale file handle

 

[fiona]

Hi,
please see the following thread: https://forum.proxmox.com/threads/smb-cifs-mount-point-stale-file-handle.124105/post-540218
TL;DR: you might need to set the noserverino mount option in the storage configuration: pvesm set <storage ID> --options noserverino (and unmount and wait for it to be mounted again afterwards).

 

[ClandestineAvacado]

Hi,
please see the following thread: https://forum.proxmox.com/threads/smb-cifs-mount-point-stale-file-handle.124105/post-540218
TL;DR: you might need to set the noserverino mount option in the storage configuration: pvesm set <storage ID> --options noserverino (and unmount and wait for it to be mounted again afterwards).

Thanks Fiona - I read that last night and will read again more carefully! Something (maybe?) weird before I head to work and think about this all day:

In the pve host's /mnt/ I see these mnts:

root@pve:/mnt/pve# ls -la
total 28
drwxr-xr-x 8 root root 4096 Jan 10 16:57 .
drwxr-xr-x 4 root root 4096 Jan  9 17:30 ..
drwxr-xr-x 2 root root 4096 Jan  9 19:40 BUP
drwxr-xr-x 6 1000 1000 4096 Jan  9 17:10 ip62_nfsshare
drwxr-xr-x 2 root root 4096 Jan 10 16:47 public
drwxr-xr-x 2 root root 4096 Jan 10 16:31 Samba-Public
drwxr-xr-x 2 root root 4096 Jan  9 19:57 seagate1tb
drwxr-xr-x 2 root root    0 Jan 10 16:57 smb-public

smb-public (note lower case) is the ID/name I gave the share in question. I'm unsure why the other mnts are appearing, as I assumed I would only see mnts I established in the Storage settings. What is weird to me (and possibly part of my problem) is that the list above shows all the shares from my Raspberry Pi based Samba config (public, Samba-Public, and seagate1tb) AND smb-public, which is the ID I gave

Here is the config in the PVE for smb-public


Here is my storage list

 

[fiona]

smb-public (note lower case) is the ID/name I gave the share in question. I'm unsure why the other mnts are appearing, as I assumed I would only see mnts I established in the Storage settings. What is weird to me (and possibly part of my problem) is that the list above shows all the shares from my Raspberry Pi based Samba config (public, Samba-Public, and seagate1tb) AND smb-public, which is the ID I gave

Hmm, did you ever mount/configure those other shares in the past? Are they actually mounted right now (you can check the output of findmnt for example)?

Here is the config in the PVE for smb-public
View attachment 61280

The mount options cannot currently be configured via UI, only via CLI. See the command from my last reply and the other thread.

 

[ClandestineAvacado]

Hmm, did you ever mount/configure those other shares in the past? Are they actually mounted right now (you can check the output of findmnt for example)?

Apparently, I did! I wiped those old mounts out, and kept only the one, and it seems to have backed up without the previous error. Solved, thank you!