1

I made a script for my Proxmox host to make a copy of its daily backups to another machine (running Windows Server 2022).

The script mounts a NFS share from the Windows host and runs this rsync command:

rsync -ahzP --stats --update --delete-before --delete-excluded --exclude "*.log" /mnt/raid/ /mnt/backups > /root/ext_backup.log

It runs for about 30 minutes and then it throws this error:

rsync: [receiver] write failed on "/mnt/backups/backups/dump/vzdump-qemu-101-2022_01_23-00_00_01.vma.zst": Input/output error (5)
rsync error: error in file IO (code 11) at receiver.c(378) [receiver=3.2.3]

rsync: [sender] write error: Broken pipe (32)

What could be the problem?

On the windows machine there's all the needed space for the backup operation and the file it's not corrupted.

14
  • Can you also provide the command line you use to mount the share?
    – ZivkoK
    Commented Jan 30, 2022 at 22:37
  • @ZivkoK Sure, here it is: mount -t nfs 192.168.1.105:/pve-backups /mnt/backups
    – alex3025
    Commented Jan 31, 2022 at 7:21
  • Does it always fail at the same file (vzdump-qemu-101-2022_01_23-00_00_01.vma.zst) or is it random? If random, were you able to identify a common pattern? (large files or files in use)
    – ZivkoK
    Commented Jan 31, 2022 at 10:06
  • @ZivkoK it fails after about 30 minutes regardless of what file is transfering (if I remove that file, it will crash on the next one).
    – alex3025
    Commented Jan 31, 2022 at 10:17
  • Can you try adding a timeout option to rsync command (i.e --timeout=60) to see if it makes any difference?
    – ZivkoK
    Commented Jan 31, 2022 at 18:41

1 Answer 1

0

How I solved it:

I've discovered this forgotten post on the ArchLinux forum, and tried the solution:

It seemed to be a cache problem or something related.

To have it working, I just added -o fg,noac,lookupcache=none to the mount command.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .