public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <bsampl@gmx.at>
To: <cygwin@cygwin.com>
Subject: Error during transfer
Date: Sat, 4 Sep 2021 08:53:06 +0200	[thread overview]
Message-ID: <000001d7a159$85644020$902cc060$@gmx.at> (raw)

Hello, during a transfer today I got this error message, The last part is
always there when starting rsync, should be a problem related to windows,
but the 5 lines before are new. I would like to ask you to explain the
possible reason for this error. I just copied files from one external disk
to another on localhost. Many thanks.

----------------------------------------------------------------------------
------------------------------------------



rsync: writefd_unbuffered failed to write 4092 bytes to socket [sender]:
Broken pipe (32)

rsync: read error: Software caused connection abort (113)

rsync error: error in rsync protocol data stream (code 12) at
/home/lapo/package/rsync-3.0.9-1/src/rsync-3.0.9/io.c(764) [sender=3.0.9]

Error in rsync protocol data stream

Rsync.exe returned an error. Will try again. This is retry number 1 of 5



Executing: rsync.exe  -v -rlt -z --chmod=a=rw,Da+x --delete
--exclude='*.lrc' "/cygdrive/D/Daten/Multimedia/Musikbibliothek/Bibliothek/"
"localhost::newMusic/Bibliothek/"

      1 [main] rsync 10360 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
pointer.  Please report this problem to

the public mailing list  <mailto:cygwin@cygwin.com> cygwin@cygwin.com

----------------------------------------------------------------------------
------------------------------------------





Regards

Bernhard Sampl




             reply	other threads:[~2021-09-04  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04  6:53 bsampl [this message]
2021-09-04  6:55 ` cygwinautoreply
2021-09-07  6:39 ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001d7a159$85644020$902cc060$@gmx.at' \
    --to=bsampl@gmx.at \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).