On Wednesday 15 December 2004 7:19 pm, david rankin wrote:
try:
rsync -a --delete-after /home/pwa/ /home-backup/pwa
Alas -- pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images. Paul
On Wednesday 15 December 2004 07:43 pm, Paul W. Abrahams wrote:
On Wednesday 15 December 2004 7:19 pm, david rankin wrote:
try:
rsync -a --delete-after /home/pwa/ /home-backup/pwa
Alas --
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Paul
I tried a similar situation on my machine here, even without the slashes, and it works. (doesn't give the desired result without the slashes, but it doesn't give errors). Something is broken on your machine... either rsync or something in those files. Can you copy that directory using cp -par ??
On Wed, 15 Dec 2004, Paul W. Abrahams wrote:
On Wednesday 15 December 2004 7:19 pm, david rankin wrote:
try:
rsync -a --delete-after /home/pwa/ /home-backup/pwa
Alas --
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Basically, the only time I've ever seen that is when rsync gets
"confused", which is *quite* rare. I *have* seen it happen, although
that was quite some time ago.
Try this:
cd /home/pwa
tar cf - . | tar --diff -C /home-backup/pwa
That creates a tar pipeline which will tell you what is different.
If *that* errors out (watch the /var/log/messages and friends), you've
got hardware problems (or possibly kernel, etc...).
The command does *not* write anything to disk.
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson
On Thu, 16 Dec 2004 14:21, Jon Nelson wrote:
On Wed, 15 Dec 2004, Paul W. Abrahams wrote:
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Basically, the only time I've ever seen that is when rsync gets "confused", which is *quite* rare. I *have* seen it happen, although that was quite some time ago.
The following appeared on a local LUG list which may shed some light on the problem. I have not encountered the problem myself, but then again I don't use rsync that often. ------------------------------------------ ------------------------------
I'm using --bwlimit because I have found that rsync hangs if I don't. I have no idea why. I've been slowly increasing --bwlimit to find out if there is a critical point.
There's a good idea I didn't think of. I've had this happen too and to put it bluntly "It's not rsync's fault the network can't handle the full bandwidth." - usually the receiver's network card driver or stack can't keep up, you'll probably find it works fine without the limit for good network cards with big buffers & DMA - try the opposite direction just as an experiment if you have a variety of NICs. ----------------------------------------- -------------------------------- -- Regards, Graham Smith ---------------------------------------------------------
On Thu, 16 Dec 2004, Graham Smith wrote:
On Thu, 16 Dec 2004 14:21, Jon Nelson wrote:
On Wed, 15 Dec 2004, Paul W. Abrahams wrote:
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Basically, the only time I've ever seen that is when rsync gets "confused", which is *quite* rare. I *have* seen it happen, although that was quite some time ago.
The following appeared on a local LUG list which may shed some light on the problem. I have not encountered the problem myself, but then again I don't use rsync that often.
------------------------------------------ ------------------------------
I'm using --bwlimit because I have found that rsync hangs if I don't. I have no idea why. I've been slowly increasing --bwlimit to find out if there is a critical point.
There's a good idea I didn't think of. I've had this happen too and to put it bluntly "It's not rsync's fault the network can't handle the full bandwidth." - usually the receiver's network card driver or stack can't keep up, you'll probably find it works fine without the limit for good network cards with big buffers & DMA - try the opposite direction just as an experiment if you have a variety of NICs.
Unless I'm mistaken, the error that started this thread is unique to
disk-to-disk (ie, "local") rsync invocations, and has nothing to do with
NICs or networks or anything else.
However, bwlimit might be a band-aid over a larger algorithmic or
implementation problem encountered with iffy NICs and/or drivers.
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson
Try running with more v's (2 or 3) and post the results here. On Wed, 15 Dec 2004, Paul W. Abrahams wrote:
On Wednesday 15 December 2004 7:19 pm, david rankin wrote:
try:
rsync -a --delete-after /home/pwa/ /home-backup/pwa
Alas --
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Paul
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson
One last thing, read this bug and make sure you've got the space: https://bugzilla.samba.org/show_bug.cgi?id=1457 On Wed, 15 Dec 2004, Paul W. Abrahams wrote:
On Wednesday 15 December 2004 7:19 pm, david rankin wrote:
try:
rsync -a --delete-after /home/pwa/ /home-backup/pwa
Alas --
pwa@suillus:~> rsync -a --delete-after /home/pwa/ /home-backup/pwa rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) pwa@suillus:~> rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515)
pwa@suillus:~>
I also tried it with the -v option and noticed that the failure seems to happen while copying very large files such as .iso images.
Paul
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson
participants (4)
-
Bruce Marshall -
Graham Smith -
Jon Nelson -
Paul W. Abrahams