[Mingw-notify] [ mingw-Bugs-1187848 ] copying data across UNC paths causes corruption

[SourceForge.net <no...@so...>]

Bugs item #1187848, was opened at 2005-04-21 22:34
Message generated for change (Comment added) made by jpr5
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1187848&group_id=2435

Category: msys
Group: component package
Status: Open
Resolution: None
Priority: 5
Submitted By: Jordan Ritter (jpr5)
Assigned to: Earnie Boyd (earnie)
Summary: copying data across UNC paths causes corruption

Initial Comment:
One of the coolest things I like about MinGW is the
seamless integration with UNC pathnames.  For example,
accessing a Windows File Server (anonymous login) is as
easy as:

% cd //someserver/sharename/dir/

Accessing files across UNC pathnames seems to work
great; I can read files, untar things, etc.  However,
copying data from a local location to a UNC share, as in:

% cp /tmp/foo.zip //someserver/sharename/dir/

results in corruption of the data file (md5sum of cp'd
data file does not match md5sum of local file)..  

This happens consistently, and always corrupts in the
same way (md5sum of different cp invocations of the
same file to a different destination file match).  I
thought at first that this might just be a bug in
``cp'', so I tried ``cat'' too, as in:

% cat /tmp/foo.zip > //someserver/sharename/dir/foo.zip

However, this again resulted in a corrupted data file,
although corrupted in a different way (file corrupted
by cp's md5sum does not match file corrupted by cat's
md5sum, and neither matches the local copy's md5sum)..

In each case of data copying, the md5sum's do not match
the original.  If I copy the data using the Windows
GUI, and then run md5sum on the file located on the UNC
path, the md5sum's do match, so this seems only to be a
write issue.  And I think this may be related to binary
data only, but I'm unsure.

--jordan

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

>Comment By: Jordan Ritter (jpr5)
Date: 2005-04-28 16:54

Message:
Logged In: YES 
user_id=50338

Earnie:

    I installed MSYS 1.0.11 (Snapshot) and the problem persists.  Same tests 
applied, same results experienced.

--jordan

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

Comment By: Earnie Boyd (earnie)
Date: 2005-04-25 15:28

Message:
Logged In: YES 
user_id=15438

I'm thinking this is fixed.  What version of MSYS are you
using?  Please try 1.0.11 snapshot if you're not already.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1187848&group_id=2435