This article is more than five years old and potentially contains out-dated information.
작성한지 5년 이상 지난 게시물입니다. 최신의 정보와 맞지 않는 내용을 포함할 수도 있습니다.

I encountered a very strange error message that I have never come across before. I was transferring a large file (a few gigabytes) from a computer to another using rsync.

Received disconnect from 2: Packet corrupt

I initially suspected rsync was being silly, so I tried it with scp. Same result.

Sometimes I see slightly different error messages:

Corrupted MAC on input.
Disconnecting: Packet corrupt

So I Googled around and found a number of related pages:

This is enough to lead me to believe that the on-board network interface card has some issues. Maybe I’m filling the buffer faster than it can flush out. Or it could be a nasty bug in the Linux kernel. Either way, it’s not something that I can fix very easily.

What if I slow down a bit? Would it make any difference?

As rsync manual explains:

--bwlimit=KBPS          limit I/O bandwidth; KBytes per second

I’ve tried this:

rsync -aP -e ssh --bwlimit=500 archive.tgz

It would take it to a little bit further, but it still failed.

As a temporary solution, I wrote a simple shell script:

while [ 1 ]; do
  rsync -aP -e ssh --bwlimit=500 archive.tgz
  if [ $? -eq 0 ]; then exit; fi;

This will keep trying the file transfer until rsync exits with a status code 0 which indicates a normal exit.

The only way to test my hypothesis (that it is a hardware problem) is to try the same file transfer with a different network interface card.