Symptoms

Various symptoms may be observed for a container with a highly fragmented private area:

  1. The container starts with a sharing violation error:

    Example:

    C:\Users\Administrator>vzctl start 6887

Starting container...

WARNING: (C:\vz\Private\6887\root.efd, {971890c5-833d-4857-86f7-17cc762bfda3}) sharing violation, trying nonpaged mount
Container is mounted
Container was started

  2. The container does not start with a dq_mount failed error:

    Example:

    C:> vzctl start 101 
Starting container ... 
Parallels Virtuozzo Containers API function call VZVolumeMountExW failed (C:\VZ\Private\101\root.efd, {89B53077-4330-4E33-83E9-5F9968F2E13B}) err = 32 
Parallels Virtuozzo Containers API function call dq_mount failed

  3. The container may show NTFS errors in its Event Viewer

  4. The Windows Process Activation Service may fail to start in the container

  5. The container may be operating slowly on I\O operations.

Cause

The container's private area is highly fragmented.

Check the fragmentation level as per the following Knowledgebase article:

114829 How to check a container's disk fragmentation level

Resolution

Perform disk defragmentation on the affected container. For more information, see :

114828 Disk defragmentation in containers best practices

See also:

112842 Unable to start container: VZVolumeMountExW failed

Internal content