[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  7130
Date     :  2004-02-02
Author   :  Kan Yabumoto
Subject  :  Re: XXCOPY using /CLONE not copying files >4.1GB
Size(KB) :  3


starman617 wrote:

> I had an unusual problem the other day trying to backup
> one 120GB drive to another. Both drives are connected
> on my Win2K Pro box using external firewire enclosures.
> Out of 117GB in used space (41 files total), only 26GB
> was copied, and the files that were only partially
> copied are all greater than 4.1GB. Both drives are NTFS.
> What's even stranger is that for those files > 4.1GB
> it didn't copy the same amount. XXCOPY did NOT report
> any errors during the copying -- it said it was successful.

We have not heard any large-file (>4GB) bug since it
was fully supported in v.2.82.8 (released on 2003-01-28).

-------------------------------------------------------
This problem goes back to XXCOPY's genealogy. It was
originally implemented as an enhanced XCOPY ca. 1993
and was DOS based. Even though it was ported to be
a Win32 application, it was mainly developed under
Win95/98 (tested in NT/2000). It was not until we
switched our development environment to the XP, much
of the code was mostly for Win9X. Soon after we
switched our development system to XP, we started to
support large files (>4GB) in NTFS.
--------------------------------------------------------

I have repeated many many many times that any message
that sounds like a bug report should include the version
number of the XXCOPY which is being used, and the full
command line text (and other pertinent info (which are
supplied in this case) such as Windows version,
file system time NTFS in this case).

I just went back and tested a few cases using the
current official release version (v.2.85.2) using
a 5GB file from NTFS to NTFS and also from NTFS to FAT32.

xxcopy huge_5gb.txt e:\tmpntfs\ /oe // dst: ntfs

Works fine as long as you have sufficient room
in the destination volume.

xxcopy huge_5gb.txt d:\tmpfat32\ /oe // dst: fat32

Result in error #39 (Disk Full)
The partially copied file in the destination
is deleted automatically.

Note: actually, the error number reported here is
quite misleading because the real cause is not an
insufficient amount of available space in the volume,
but that's how the error is reported (we may change
the value reported for this type of error in the
future).

> Is there a file size limit in XXCOPY's /CLONE command?

There is no specific size-related limitation on the /CLONE
command. As I said earlier, earlier versions of XXCOPY
(< v.2.82.8) had an implicit limit of the maximum file
size of 4GB which no longer exist. I don't really know
what is the upper limit of the current crop of NTFS
volume.

In conclusion, you should acquire the latest version of
XXCOPY and try again.

--------------------------------------------------------
If you are running the latest version and you observe
a problem, we need to investigate the situation more
closely. Please show the exact command line.
(Probably it is a good idea to create a log file using
the following switch

/ON:myerror.txt/OE3

and send the error log file to us.
---------------------------------------------------------

If you examine your command line and find a /WV0 switch,
that may have been contributed to your problem. Just
remove the switch from your batch file it never really
belong in a batch file. It is meant to be used as a
temporary "band aid". By /WV0, you are killing the
messenger who sounds an alarm.

Kan Yabumoto



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.