none
the system process is "locking" a directory - robocopy fails on network

    Question

  • Hi all

    I am trying to copy files between Win 2008 R2 using robocopy , but I always got the error "ERROR 32 (0x00000020) Accessing Destination Directory" .

    Process Explorer show one open handle from the "system" process.

    Why should system lock a directory?

    The full robocopy output is:

    robocopy F:\basedir_nfs_shared\subdir \\serverdr\F$\basedir_nfs_shared\subdirdr /COPY:DAT /R:0 /NP /XF *.flag 
    
    -------------------------------------------------------------------------------
       ROBOCOPY     ::     Robust File Copy for Windows                              
    -------------------------------------------------------------------------------
    
      Started : Thu Apr 18 09:21:50 2013
    
       Source : F:\basedir_nfs_shared\subdir\
         Dest : \\serverdr\F$\basedir_nfs_shared\subdirdr\
    
        Files : *.*
    	    
    Exc Files : *.flag
    	    
      Options : *.* /COPY:DAT /NP /R:0 /W:30 
    
    ------------------------------------------------------------------------------
    
    	                 126	F:\basedir_nfs_shared\subdir\
    	  *EXTRA File 		   2.8 m	arclog_ORCL_1_536_1.arclog
              ...
    	  *EXTRA File 		 717.2 m	arclog_ORCL_1_627_1.arclog
    	    New File  		  38.2 m	arclog_ORCL_1_744_1.arclog
    2013/04/18 09:21:50 ERROR 32 (0x00000020) Accessing Destination Directory \\serverdr\F$\basedir_nfs_shared\subdirdr\
    The process cannot access the file because it is being used by another process.
    
                ...
    
    	    New File  		 192.7 m	arclog_ORCL_1_751_1.arclog
    2013/04/18 09:21:51 ERROR 32 (0x00000020) Accessing Destination Directory \\serverdr\F$\basedir_nfs_shared\subdirdr\
    The process cannot access the file because it is being used by another process.
    
    
    
    ------------------------------------------------------------------------------
    
                   Total    Copied   Skipped  Mismatch    FAILED    Extras
        Dirs :         1         0         1         0         0         0
       Files :       126         0       118         0         8        92
       Bytes :  21.973 g         0  21.217 g         0  774.39 m  17.037 g
       Times :   0:00:00   0:00:00                       0:00:00   0:00:00
    
       Ended : Thu Apr 18 09:21:51 2013
                                                      
    exit code: 10

    Please note that the F:\basedir_nfs_shared\ is an nfs-shared directory, but the handle shown by ProcExplorer is on the subdirectory F:\basedir_nfs_shared\subdirdr.

    Moreover, the nfs shared is mounted as needed and umounted : when the problem happens it is not nfs-mounted by anyone

    So, what is holding this handle?

    Thanks

    Andrea

    Thursday, April 18, 2013 8:06 AM

All replies

  • check if you have permission go to the folder and create new folder.

    if everything is good type the command with " like this :

    robocopy "F:\basedir_nfs_shared\subdir" "\\serverdr\F$\basedir_nfs_shared\subdirdr" /COPY:DAT /R:0 /NP /XF *.flag



    • Edited by Bokken JO Tuesday, June 04, 2013 5:44 AM
    Wednesday, May 22, 2013 1:39 PM