You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/01/20 19:54:33 UTC

DO NOT REPLY [Bug 16270] New: - copy date bug when copying from ntfs to samba mounted drive

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16270>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16270

copy date bug when copying from ntfs to samba mounted drive

           Summary: copy date bug when copying from ntfs to samba mounted
                    drive
           Product: Ant
           Version: 1.5.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: daniel.armbrust@mayo.edu


The copy task has a java vm caused bug when it interacts with a samba mounted
file system from linux/unix machine while the ant task is running on a windows
machine.

I had 3 different files that I created on the ntfs drive (all done from a W2K
machine).  I then copied the three files to the samba share mounted drive.
Here are the last 5 digits of the time stamps that the java vm reports.  I don't
understand its behavior... As some round down, and some up.  

			File a	File b	File c
Local NTFS		35062	87359	18093
Mounted via samba	36000	88000	18000

As you can imagnine, this leads to a lot of unnecessary file copying by the copy
task, as file c would have been recopied, even though it doesn't need to be.

To fix this, I added a dateSlop feature to the copy so that it would only copy
files that are more than 1 second apart from each other in their time stamps
when dateSlop is set to true.  

I don't know ant well enough, however to know all the implications of this
change.  This bug is annoying when it is used to copy large amounts of files. 
It also turns into a showstopper for the new synchronize task that has been
posted as a requested enhancement, when it is used to synchronize a ntfs drive
with a samba mounted drive... you end up copying upwards of 1/2 of the files in
your set (even if none of them have actually changed)

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>