Search results

Every time I launched it manually didn't fail. Maybe is possible the let the backup procedure use strace? Mirco

Hi fl0moto. I will investigate it but think is not the same problem. mount's man page says noserverino option has to do with how to treat hardlinks, which are not present among the files I backup. Thank you anyway.

Hi Inglebard, the problem rises really sparsely. Now it's 10 days since last happening. I will investigate fl0moto's advice but I think that's not the case.

I have troubles backing up an LXC container on PROXMOX VE 9. I do it as a backup job that saves shapshot images on a NAS. Strange thing is that it happens sometimes, not always. Traced error is: 2026-01-10 01:05:02 INFO: zstd: error 70 : Write error : cannot write block : Bad address Backup...

Never did such a thing. Just found some references to bind-mounting in a chroot-ed environment, I'll dig deeper. Thanks a lot for the immediate response. Mirco

I have an SMB host sharing some folder on the same LAN where mycontainer is set up. After having regularly installed cifs support: admin@mycontainer:~$ sudo apt install cifs-utils I'm not able to mount a share; issuing: admin@mycontainer:~$ sudo mount -t cifs -o vers=1.0,username=myusername...