sync prob with big files

fuzzy_4711 fuzzy_4711 at gmx.de
Sat Dec 10 07:48:18 MST 2011


Hi list.

> I gave it another try and started it after ssh to the box using this
> command:
> nohup ./ic_scripts/executedByCron/sync_NAS_devices.sh >>
> /var/log/rsync.log 2>&1 &
> 
> This is what I got now:
> -rwxrwxrwx 1 bacula pulse    157810688 Dec  9  2011 .bkp-nas-0002.Ysteoo
> 
> This must be what you expect as a regular rsync temp file name, I guess.
> 
> The file is growing. Let's wait and see, I'll report later. 

I still get an exit code 1 for my rsync call in the shell script.
Nevertheless I got some output from redirecting to /var/log/rsync.log.
Here it is:

rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/bkp-nas-0003": Invalid
argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/bkp-nas-0004": Invalid
argument (22)
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]:
Broken pipe (32)
rsync: close failed on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/.bkp-nas-0002.Ysteoo":
Input/output error (5)
rsync error: error in file IO (code 11) at receiver.c(731) [receiver=3.0.7]
rsync: connection unexpectedly closed (53 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[sender=3.0.7]

FYI: The files bkp-nas-003/4 are there already (at the target). The tmp
file (*0002*), written by rsync is gone. On my last manual check, the
file size of the tmp file almost reached the size of the source file.

I decided to run a test on a much smaller file set. Exit code is 1
again. BUT, the files are all synced to the target. The whole dir and
scripts are 188K only. Here is my log for that:

rsync: chown
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/."
failed: Invalid argument (22)
rsync: chown
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron"
failed: Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/.tuning_primer.sh.Eca4xb":
Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron/.crontab_dump.sh.Iz8MrN":
Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron/.mysql_backup_databases.sh.cUq3mp":
Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron/.mysql_flush_and_move.sh.aepRj1":
Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron/.remove_files_older_than_keep_days.sh.QMwciD":
Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron/.sync_NAS_devices.sh.w7I7hf":
Invalid argument (22)
rsync: failed to set times on
"/mnt/NAS_192.168.1.8_FOR_SYNC/backup_sync_from_1.9_to_1.8/sl-test/executedByCron/.sync_NAS_devices.sh.old.yvSEjR":
Invalid argument (22)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1042) [sender=3.0.7]

Does anybody know what Invalid argument (22) would like to tell?
Thank you.


-fuz




More information about the rsync mailing list