Mount and Export failures with error "There is not enough space on the disk." (4032760)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Mount and Export failures with error "There is not enough space on the disk."
Description

In a Core server, there can be an issue encountered when mounting a recovery point for any volume that is of significant size. In case there is a certain amount of free space left on the C: drive that would be insufficient to perform a mount.
Application UI error displays:
IOException
There is not enough space on the disk.
Hide stack trace
System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.IO.IOException: There is not enough space on the disk. at System.IO.Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.SetLengthCore(Int64 value) at Replay.Core.Implementation.Repositories.FileAbstraction.Indexes.FileBasedIndexEntriesMap.InitializeIfNeeded() at Replay.Core.Implementation.Repositories.FileAbstraction.Indexes.FileBasedIndexEntriesMap..ctor(Action releaseCallback, UInt64 volumeTotalCapacity, String mapPath) at Replay.Core.Implementation.Repositories.FileAbstraction.Indexes.IndexEntriesMapService.LoadIndexes(IFileVersionIndexManager fileVersionIndexManager, IEnumerable1 incrementalIndexFileIds, String key, UInt64 volumeTotalCapacity, Action2 progressCallback, CancellationToken cancellationToken) at Replay.Core.Implementation.Repositories.FileAbstraction.Indexes.IndexEntriesMapService.<>cDisplayClass7.b6() at System.Threading.Tasks.Task1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of inner exception stack trace --- at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at Replay.Core.Implementation.Repositories.FileAbstraction.Indexes.IndexEntriesMapService.GetOrBuildMap(IList1 incrementalIndexFileIds, UInt64 baseIndexFileId, IFileVersionIndexManager fileVersionIndexManager, UInt64 totalCapacity
For export errors, logs may also show:
ERROR 2015-09-22T10:44:04 [1286] - Replay.Core.Implementation.Export.VirtualMachineExporterWindows (Post-processing volume(s))
Mounting ''xxxxx' on vcenter target 'xxxxx'' at 'C:\ProgramData\AppRecovery\ExportMounts\xxx_9bdfae6e-b50f-4d7d-bee9-e3cb3d886797' was not successful

INFO  2015-09-22T10:44:04 [1286] - Replay.Core.Implementation.Export.VirtualMachineExporterBase ()
Completed export of VM 'xxxx' on vcenter target 'xxxx'
  Disk export results:
    \\?\PhysicalDrive0 - RanToCompletion  Exception text: null
    \\?\PhysicalDrive1 - RanToCompletion  Exception text: null

  Volume export results:
    C:\ - RanToCompletion  Exception text: null
    D:\ - Faulted  Exception text: There is not enough space on the disk.

  Disk-specific exception details:

  Volume-specific exception details:
    D:\ - System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.IO.IOException: There is not enough space on the disk.
Cause

Index Maps are created in the IndexEntriesMap path. These Index Maps will consume 1 GB of free space for every 1 TB of volume size. For instance, if you have a 5 TB volume (total available size of the volume) then you need a minimum of 5 GB free space for the Index Map to be created.
Resolution

To resolve this issue:
1. Determine the amount of free space on the C: volume where the mount points are performed by default.
2. Calculate how much free space is needed to restore the volume (either incremental or base) of a recovery point at that point in time.
For example, if a H: volume is 8TB in size, then there needs to be a minimum of 8GB in free space on C:.
3. If there is less than the required amount, then do one of the following steps:
a. the C: drive would need additional space added or extended if it is a VM or,
b. the location of the index files can be changed to another location having sufficient disk space.
4. Perform a mount of the volume.
In case the disk space on the C: volume cannot be increased, change the path where the mount points index files are created as follows on the Core server:
1. Open the Registry Editor by clicking the Start button, typing "regedit" into the Search box, and then pressing ENTER. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
2. Navigate to the path HKLM\Software\AppRecovery\Core\IndexEntriesMapService
3. Edit the entry from the C: to go to the new location where there is sufficient space to create the index file.
4. Restart the core service.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Mount and Export failures with error "There is not enough space on the disk." (4032760)

Title

Description

Cause

Resolution

Leave a Comment