public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wayne Davison <wayne@opencoder.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Cygwin: 2.6.0, rsync 3.1.2, "file has vanished"
Date: Mon, 28 Nov 2016 22:41:00 -0000	[thread overview]
Message-ID: <CAHSx_SvoKA3pBhLaqg4BQ9J-2C2rq8cTgmZWT7C=_fK1OoZYMA@mail.gmail.com> (raw)
In-Reply-To: <cba315e68e3e97d97e54c33070fefd9e@192.168.11.198>

On Sun, Nov 27, 2016 at 11:07 PM, Shaun Maher <shaun@mach.com.au> wrote:
>   file has vanished: "BackUps(old)/Backup Pre-Rolled Payroll 2015"16-MBTT2016.zip" (in VSSG)

Those file-has-vanished errors shouldn't be affected by the --iconv
option because that is a sender-side error, and the rsync sender
directly reads file names via readdir() and then tries to stat() those
names (it is the receiving side that might get converted names via the
--iconv translations).

So, the question is: why is rsync getting a filename via readdir that
it can't stat?  Can you try out this C program:
http://opencoder.net/list-and-stat.c

You compile it with gcc ("gcc -o list-and-stat list-and-stat.c") and
then run it with a directory name where one of your problem files
exists. It will output things like this:

74 65 73 74 e2 b8 b1 66 69 6c 65 | test⸱file

If you see a "FAILED to stat" message, send the byte sequence for that
file to the list and mention what filesystem type it is mounted on.

If it doesn't generate an error, what rsync version are you using? Is
it the cygwin version or something else?

The error indicates that an rsync daemon module is involved (the "in
VSSG" bit), so you might try a manual rsync copy of a problem file and
see if the issue is the daemon context or rsync in general.

..wayne..

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-11-28 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 17:24 Shaun Maher
2016-11-28 19:53 ` Brian Inglis
2016-11-28 22:41 ` Wayne Davison [this message]
2016-11-29 14:25 Shaun Maher

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='CAHSx_SvoKA3pBhLaqg4BQ9J-2C2rq8cTgmZWT7C=_fK1OoZYMA@mail.gmail.com' \
    --to=wayne@opencoder.net \
    --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).