Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
The CloudDrive Mount Operation Takes a Long Time to Complete

The CloudDrive Mount Operation Takes a Long Time to Complete

Updated: July 24, 2015

Symptom: When you call the Mount method to mount a drive containing very large numbers of files, the mount operation takes longer than expected to complete or times out.

Cause: The problem is caused by a known issue that occurs when the drive being mounted contains hundreds of thousands or even millions of files. The majority of the time taken performing the Mount operation is spent updating the Access Control Lists (ACLs) on all of the drive’s files. The API attempts to change these ACLs on the root of the drive so that lower privileged roles, such as web and worker roles, will be able to access the contents of the drive after it is mounted. However, the default settings for ACLs on an NTFS file system is to inherit the ACLs from the parent, so these ACL changes are then propagated to all files on the drive.

Resolution: To resolve this issue and greatly lessen the time taken by the Mount operation, you need to turn off automatic ACL inheritance for the operation. To break the ACL inheritance chain, mount the drive, open a command shell, and then run the following commands, replacing “z:” with the letter of the mounted drive:

cd \
icacls.exe * /inheritance:d

icacls.exe will print out a list of files and directories it is processing, followed by some statistics:

processed file: examplefile1
processed file: examplefile2
Successfully processed 2 files; Failed processing 0 files

Finally, you should unmount the drive. Subsequent calls to Mount should be performed much faster.

See Also


Known Issues in Azure Cloud Services



© 2015 Microsoft