Skip to main content
Contact Us
Register
Pure Technical Services

Storage vMotion using VVOL datastore on Pure array results in Error 195887107

  1. Last updated
  2. Save as PDF

Currently viewing public documentation. Please login to access the full scope of documentation.

Problem

When attempting a Storage vMotion using a VVOL datastore on the PureStorage array, the operation results in the following error:

Failed writing for data. Error 195887107. Not found. 

Taking a look within vmware.log for the VM, we can see the below error:

vmware-1.log:2018-12-04T18:01:20.529Z| Worker#0| W115: Mirror: scsi0:1: SVMotionLocalDiskCreate: Failed to create destination disk: The requested size is not a multiple of 1MB
vmware-1.log:2018-12-04T18:01:20.529Z| Worker#0| W115: SVMotionPrepareForCopyThread: Failed to create destination disks

Impact

Storage Vmotion Failure.

Solution

The issue regarding Storage vMotion can be due to an invalid disk size setting for the VM, on the VVOL datastore.  In this case, the destination machine disk size was not an integer - rather, when the settings were edited for disk size, the data file showed a size of 1,530.3999992320505 MB.

As per VMware documentation below, the size of a virtual volume must be a valid integer:

https://docs.vmware.com/en/VMware-vS...gHsAzPOAIxAF8g

"The size of a virtual volume must be a multiple of 1 MB, with a minimum size of 1 MB. As a result, all virtual disks that you provision on a virtual datastore or migrate from any datastore other than the virtual datastore should be an even multiple of 1 MB in size. If the virtual disk you migrate to the virtual datastore is not an even multiple of 1 MB, extend the disk manually to the nearest even multiple of 1 MB."