From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rsync failed after windows 10 update
Date: Mon, 04 Mar 2019 12:36:00 -0000 [thread overview]
Message-ID: <20190304123608.GE3785@calimero.vinschen.de> (raw)
In-Reply-To: <1551701612886-0.post@n5.nabble.com>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
On Mar 4 05:13, jwang wrote:
> Error message via strace:
>
> 1238 99433 [main] rsync 10684 getwinenv: can't set native for HOME= since
> no environ yet
> 3295 164392 [main] rsync 10684 transport_layer_pipes::connect: Try to
> connect to named pipe: \\.\pipe\cygwin-e022582115c10879-lpc
> 199 164591 [main] rsync 10684 transport_layer_pipes::connect: Error
> opening the pipe (2)
> 138 164729 [main] rsync 10684 client_request::make_request: cygserver
> un-available (/etc/cygserver.conf not in office either, nor on asus)
> 109 282075 [main] rsync 10684 fhandler_pipe::create: name
> \\.\pipe\cygwin-e022582115c10879-pty0-from-master, size 131072, mode
> PIPE_TYPE_MESSAGE
> 188 282263 [main] rsync 10684 fhandler_pipe::create: pipe busy
> 84 416660 [main] rsync 10684 fhandler_base::open:
> (\??\C:\cygwin64\home\james\.popt, 0x108000)
> 154 416814 [main] rsync 10684 seterrno_from_nt_status:
> /home/corinna/src/cygwin/cygwin-2.10.0/cygwin-2.10.0-1.x86_64/src/newlib-cygwin/winsup/cygwin/fhandler.cc:680
> status 0xC0000034 -> windows error 2
^^^^^^^^^^^^^^^^^
This looks like a problem I only found this weekend. Do you have WSL
activated? If so, can you please do two things:
First, install the latest developer snapshot from
https://cygwin.com/snapshots/. This is essential!
Second, check with `lsattr' if all or some of the directories you're
trying to rsync have the "case-sensitivity" flag set, e.g.
$ lsattr -d foo
---------n-C foo
That means the flag is set. Remove the flag recursively, e.g.
$ chattr -R -C foo
Now try rsync again.
Here's what I found two days ago:
https://github.com/Microsoft/WSL/issues/3885
The developer snapshot is needed so that Cygwin does not create
case-sensitive directories by default. I'd released 3.0.2 with
this patch already but I'm still waiting for a report to a certain.
problem.
HTH,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-04 12:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 12:19 jwang
2019-03-04 12:36 ` Corinna Vinschen [this message]
2019-03-04 14:44 ` jwang
2019-03-05 9:46 ` jwang
2019-03-05 12:04 ` Corinna Vinschen
2019-03-05 13:16 ` jwang
2019-03-05 15:25 ` jwang
2019-03-06 10:00 ` jwang
2019-03-06 11:57 ` Corinna Vinschen
2019-03-06 12:05 ` jwang
2019-03-06 12:14 ` Corinna Vinschen
2019-03-06 14:00 ` jwang
2019-03-08 13:59 ` jwang
2019-03-08 14:18 ` Houder
2019-03-08 15:35 ` jwang
2019-03-08 20:59 ` Jerry Baker via cygwin
2019-03-09 1:23 ` jwang
2019-03-09 9:16 ` jwang
2019-03-11 15:02 ` jwang
2019-03-12 10:29 ` jwang
2019-03-16 8:36 ` jwang
2019-03-16 10:30 ` Houder
2019-03-16 10:49 ` jwang
2019-03-16 12:45 ` Houder
2019-03-16 13:13 ` jwang
2019-03-16 13:19 ` jwang
2019-03-16 13:26 ` jwang
2019-03-16 13:46 ` Houder
2019-03-16 14:18 ` jwang
2019-03-16 13:31 ` Houder
2019-03-17 6:45 ` Achim Gratz
2019-03-17 8:15 ` jwang
2019-03-17 9:07 ` Eliot Moss
2019-03-18 9:47 ` jwang
2019-04-02 8:45 ` jwang
2019-03-05 12:20 ` Andrey Repin
2019-03-05 13:15 ` jwang
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=20190304123608.GE3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).