i was usually have scripts update but i was doing a manual copy for a new share

and i noticed

i see now

[sender] expand file_list pointer array to 4096 bytes, did move
[sender] expand file_list pointer array to 1024 bytes, did move
[sender] expand file_list pointer array to 4096 bytes, did move
[sender] expand file_list pointer array to 16384 bytes, did move
[sender] expand file_list pointer array to 32768 bytes, did move
[sender] expand file_list pointer array to 65536 bytes, did not move
[sender] expand file_list pointer array to 131072 bytes, did not move
[sender] expand file_list pointer array to 262144 bytes, did move
[sender] expand file_list pointer array to 524288 bytes, did move
[sender] expand file_list pointer array to 1048576 bytes, did move
[receiver] expand file_list pointer array to 524288 bytes, did move
[generator] expand file_list pointer array to 524288 bytes, did move

or at end of the file says uptodate..

i find rsync locks up more now doesnt say incremently list

i also got it hanging after 30 min run protocol incompatibility

this is my code i use in a script i altered it for just command line test

rsync -avzue ssh --exclude-from='/boot/config/plugins/user.scripts/scripts/exclude1.txt' --protect-args -avue ssh --stats --numeric-ids --progress '/mnt/user/Documents/' root@$serverip:'/mnt/user/Backup Files/Mikes Files/Documents/'

so did things change? get more glitchty etc

and or are some the rsync commands no longer used anymore??

and what is this sender, receiver, generator really meaning

and this error constantly comes up after a while

rsync error: protocol incompatibility (code 2) at receiver.c(358) [receiver=3.4.3]

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

and if i keep running my command after so long it craps out with protocol data stream code 12

rsync error: error in rsync protocol data stream (code 12) at io.c(232) [generator=3.4.3]

rsync: [sender] write error: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(849) [sender=3.4.3]

its like rysnc can no longer transfer 4 tb over 1 million files anymore its like it has a fit.. is there a way to fix it like it used to work fine since this is constantly broken and then the hard drives spin down and rysnc still running supposeldy saying uptodate or the other stuff and the drives arent even running and i running like less then 2 meg a sec copying

has rsync busted in unraid 7.3.1

rsync error: protocol incompatibility (code 2) at receiver.c(358) [receiver=3.4.3]

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

Edited June 19Jun 19 by comet424

rsync got some issues in the version that 7.3.1 includes, not sure if that is the source of your problem.

https://github.com/RsyncProject/rsync/issues/915

im doing unraid to unraid rysncing so 7.3.1v to 7.3.1v

i even finding if i do windows copy unraid share to 2nd unraid share it stalls out too the 4.5TB copy

small copies seem fine but when you try to copy everything then it just craps itself it seems

if i stop copying and restart the 4.5tb 1.6+ mil files i find it doesnt copy says it is the files keep running through the file names but nothing happening

going to let it keep copyingg see if it catches up what it copied but since 7.3.1 things just seem a bit buggy here and there

Edited June 19Jun 19 by comet424

cuz even with windows copying the files are spinning through there is no disk activity on 2nd unraid server or main unraid... unless cuz the files are small files its just going through them fast. and not registering a speed..

as ive tried copying the same 4tb folder of my desktop files of computer backups and ive been trying last 4 days before i tried asking help on here

any my logs are full of

Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1
Jun 19 03:59:09 Tardis nginx: 2026/06/19 03:59:09 [error] 1409846#1409846: MEMSTORE:00: force-reaping msg with refcount 1

which i constantly see alot of times and googling never helps it doesnt say what caused it

and its copying tardis desktop files to backupserver desktop files

tardis-diagnostics-20260619-0530.zip backupserver-diagnostics-20260619-0530.zip

Edited June 19Jun 19 by comet424