error writing 4 unbuffered bytes - exiting
darryl at harvey.net.au
Tue Jun 18 01:58:01 EST 2002
I am running a fairly new box, Athlon 1.4Ghz, 512 Mb RAM, RedHat 7.3, rsync
rsync version 2.5.4 protocol version 26, it's disk layout is;
bash-2.05a# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 372M 338M 15M 96% /
/dev/sda1 45M 8.9M 34M 21% /boot
/dev/sda5 703M 218M 449M 33% /home
none 251M 0 251M 0% /dev/shm
/dev/sda2 1.9G 1.7G 101M 95% /usr
/dev/sda7 251M 130M 107M 55% /var
/dev/hda1 19G 2.3G 16G 13% /usr/local/backup
/dev/hda2 17G 2.6G 14G 16% /opt/archive
I am trying to maintain a rsync'ed copy of the data from most of the
filesystems onto /opt/archive.
(in fact the complete command I am using is);
rsync -vaW --exclude /opt/ --exclude /proc/ --exclude /dev/ --exclude /mnt/
--exclude /lost+found/ --exclude /tmp/ --delete -T /tmp / /opt/archive
Note this is the ONLY thing the /opt/archive filesystem is used for. I run
rsync every three hours to make sure it is up to date..
Just recently I have been getting these errors;
rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(464)
rsync: error writing 69 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(464
And the rsync fails.
I read in the archives and "Current Issues" Section of the web site that
this is a known issue and it says that fatal error messages from the remote
machine gets lost along the way.
This is running on the same..
As you can see, the destination disk has 14Gb free, so we are not running
out of disk space, but it really does mainly occur on LARGE file sizes.
Testing the drive speeds, I do not see any problem either as /dev/hda2 is
the FASTEST drive I have.
Timing buffered disk reads: 64 MB in 10.48 seconds = 6.11 MB/sec
Timing buffered disk reads: 64 MB in 3.31 seconds = 19.34 MB/sec
Timing buffered disk reads: 64 MB in 2.57 seconds = 24.90 MB/se
Any ideas ???
More information about the rsync