Unable to create virtual machine in VirtualStore due to VxFS Disk Layout Version (DLV)
|Article:TECH145045|||||Created: 2010-11-26|||||Updated: 2010-11-27|||||Article URL http://www.symantec.com/docs/TECH145045|
Unable to create virtual machine in VSphere when datastore is VirtualStore. Error message in client is "Virtual machine <Virtual Machine Name> has disks attached which are not on Symantec Virtualstore datastores"
VSphere client error:
Virtual machine <Virtual Machine Name> has disks attached which are not on Symantec Virtualstore datastores
[root@sfm_cms2 logs]# cat /var/opt/VRTSsfmh/logs/error.log
Number of vmdks attached to the vm/template = 1
checksvsconfig:/vmimages filesystem version (=7) too low. Filesnap feature not supported for this version.
checksvsconfig:10.12.251.82 /vmimages NOT found on this SVS cluster.
Virtual machine has a disk([svs store] New Virtual Machine/New Virtual Machine.vmdk) attached which is not hosted on Symantec Virtual Store
This error is due to the VxFS file system Disk Layout Version used in the VirtualStore cluster, that provides a backing store for the Virtual Machine images. VxFS Disk Layout Version 8 (DLV8) is required for VirtualStore, which provides the FileSnap functionality
The VxFS Disk Layout Version can be checked by logging into one of the VirtualStore nodes and using the fstyp command to query the volume that contains the file system. In the following example the volume vmimages in the svsdg diskgroup has VxFS Disk Layout Version 7:
[root@sfm_cms2 logs]# fstyp -v /dev/vx/dsk/svsdg/vmimages | grep version
magic a501fcf5 version 7 ctime Thu 25 Nov 2010 15:44:43 GMT
This example shows volume vmimages2 that contains VxFS Disk Layout Version 8:
[root@sfm_cms2 logs]# fstyp -v /dev/vx/dsk/svsdg/vmimages2 | grep version
magic a501fcf5 version 8 ctime Fri 26 Nov 2010 14:30:02 GMT
The solution is the re-create the data file systems on the VirtualStore cluster with a Disk Layout version 8. Re-creating the file systems will destroy any data that currently resides on them. Any existing data should be backed uped and restored when they are re-created.
Article URL http://www.symantec.com/docs/TECH145045