rsync 2.6.9-2 cannot sync file with special long filename
Brian Dessent
brian@dessent.net
Sun Dec 23 16:54:00 GMT 2007
Michael wrote:
> I assume this is a bug in rsync or bash, and I believe the colon is
> causing the trouble.
You are correct that the colon is the problem, but it is not a bug.
This is a restriction imposed by the design of Windows -- there are a
number of characters that Windows does not allow in filenames and the
colon is one of them. You can see a full specification here:
<http://msdn2.microsoft.com/en-us/library/aa365247(VS.85).aspx>
In this case, NTFS reserves the colon to denote alternate data streams.
There's nothing that rsync or Cygwin can do to change that.
> Does anyone know a workaround?
You can use a managed mount as a workaround. This causes Cygwin to
encode characters that Windows won't allow in filenames with a quoted
version. It only works for Cygwin applications, obviously, as if you
look at the filenames using a non-Cygwin application they will look like
gibberish because of the encoding. It also shortens the effective
maximum file/path length because each character that is encoded
effectively takes three characters in the real filename.
> If no - is it enough
> to post the bug here, or is there another bug reporting channel for cygwin?
This is the correct place to report problems, but again this is not a
bug.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list