Re: Windows client XCOPY.EXE problem.

The INVALID_HANDLE error is returned to the SMB/CIFS client
when a directory search identifier received from the client
cannot be found in the queue of active searches.  It appears
that the directory search code is not thread safe.   The problem
in this case is more then likely caused by an a failure to
properly handle reference counts.

I was going to ask the rhetorical question "how many more
situations like this are we going to find?" but I realize the
answer is "however many struct types which have not yet been
examined for thread safety."

Jeffrey Altman



Jeffrey Altman

Rodney M Dyer wrote:

> OpenAFS Bug Tracking RT ticket:  15871
> 
> Problem:
> 
> When copying a very large tree of directories and files out of
> AFS to a local drive with the Windows XCOPY.EXE command, there exists
> the potential for XCOPY to fail with an "Invalid Handle" error.
> 
> What we know:
> 
> * The number of directories in our testing was greater than
> 500,000. The number of files was greater than 400,000.
> 
> * The XCOPY doesn't always stop with the error at the same
> location in the tree each time the copy is tried.
> 
> * If the same tree of directories and files exists on an NTFS
> drive, then XCOPY works without failing.
> 
> * WinZIP, the DOS 'FOR /r' command, and DIR /s all perform without
> issues.
> 
> * XCOPY fails even if provided the '/L' argument to only list the
> files that would be copied.
> 
> 
> Rodney M. Dyer
> Windows Systems Programmer
> Mosaic Computing Group
> William States Lee College of Engineering
> University of North Carolina at Charlotte
> Email: [email protected]
> Web: http://www.coe.uncc.edu/~rmdyer
> Phone: (704)687-3518
> Help Desk Line: (704)687-3150
> FAX: (704)687-2352
> Office: 267 Smith Building
> 
> _______________________________________________
> OpenAFS-Win32-devel mailing list
> [email protected]
> http://lists.openafs.org/mailman/listinfo/openafs-win32-devel