rsync - Dec 2024 - rsync: [sender] read errors mapping "file" : Input/output error (5)

-> Did you re-read the data and compare checksums ?

Don't know how to do this.

-> 2nd thought: What file systems do you use, and is there a peculiar size
of the file, hitting a limit?
Do I read this correct, rsync throws the error at
320,072,933,376, then continues to
640,302,152,539 bytes (file size) ?

I don't know. What I know is that almost every big file reaches the 99 % /
100% of completeness and then I get the IO error and the file is deleted.
Anyway,the usage of these parameters helped me to complete and keep the
file saved on the disk even if I got the error :

root at Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
--inplace --append --partial Free
BSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD

rsync: [sender] read errors mapping
"/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatter.img":
Input/output error (5)
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(701) [sender=3.2.4dev]
rsync error: received SIGUSR1 (code 19) at main.c(1598) [generator=3.2.4dev]

My sensation is that there is some bug or something that I have installed
on the Linux and FreeBSD file system (ext4 and ZFS) that interferes with
the transfers of big files. Maybe a disk driver of some sort.


On Mon, Dec 23, 2024 at 10:54?PM Hardy via rsync <rsync at
lists.samba.org>
wrote:
>
> On 23.12.24 20:44, Mario Marietto via rsync wrote:
> > What would you think if I told you that using Windows I no longer had
> that problem ?
> > Would you still think that there are hardware problems ?
> > And if so, why would they only manifest themselves using Linux and
> FreeBSD and not using Windows?
>
> Did you re-read the data and compare checksums?
> Sometimes Windows is not so good in passing HW errors to user programs.
>
> 2nd thought: What file systems do you use, and is there a peculiar size of
> the file, hitting a limit?
> Do I read this correct, rsync throws the error at
> 320,072,933,376, then continues to
> 640,302,152,539 bytes (file size) ?
>
> Hardy
>
> --
> Please use reply-all for most replies to avoid omitting the mailing list.
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>

-- 
Mario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20241223/420f0127/attachment.htm>

On 23.12.24 20:44, Mario Marietto via rsync wrote:
> What would you think if I told you that using Windows I no longer had that
problem ?
> Would you still think that there are hardware problems ?
> And if so, why would they only manifest themselves using Linux and FreeBSD
and not using Windows?
Did you re-read the data and compare checksums?
Sometimes Windows is not so good in passing HW errors to user programs.

2nd thought: What file systems do you use, and is there a peculiar size of the
file, hitting a limit?
Do I read this correct, rsync throws the error at
320,072,933,376, then continues to
640,302,152,539 bytes (file size) ?

Hardy