|
i have had this happen to me with a different kind of transfer. i investigated very closely and found that a certain binary data pattern that included a lot of zero bytes resulted in mistiming of the deserialization of the ethernet bit stream. it was an Intel interface card. it resulted in an IP packet error. it happened every time the source resent that packet with the same data from that point in the file. i was sending it using rsync. i worked around it by turning on compression (which used more CPU).
i don't know if your problem is the same. maybe you can compress that big file and try again, uncompressing it afterwards.
since your case freezes at 0% there may be other issues involved, such as failing space checks, triggered defragmentation, etc.
|
