Issue with .vmdk file spread over 2 luns

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I have got a NetApp filer. I have created a volume of 4 GB on it.
   Then created 2 LUNs of 2 GB each on it. Then I exposed these 2 LUNs to a   
   VMWARE ESX machine and also to a windows machine(through iSCSi intiator)
2. Through, the VMWARE ESX server, I have created a single datasource, and   
   have added these two LUNs to that datasource.
3. Then, I have installed a Windows VM (of size around 3 GB) on this 
   datasource. This means, that this 3 GB data is spread across the two 2 
   GB LUNs.
4. I can see these two partitions on the Windows machine in disk 
   management.
5. Now, I am trying to read and copy the .vmdk file on the local drives of  
   the windows machine. While doing this, it will copy the part of .vmdk
   file present on the 1st lun, but wont continue copying from the second 
   lun. 
6. I would like to know if I can copy both parts of the .vmdk files either 
   by this driver, or by making some changes to the source code?

Original issue reported on code.google.com by manasmu...@gmail.com on 24 Mar 2009 at 7:48

[GoogleCodeExporter]

Below is the error message that i get:

Exception in thread "main" java.lang.Exception: VMFS FSInfo block not found
    at com.fluidops.tools.vmfs.VMFSDriver.readVmfsInfo(VMFSDriver.java:558)
    at com.fluidops.tools.vmfs.VMFSDriver.openVmfs(VMFSDriver.java:793)
    at com.fluidops.tools.vmfs.VMFSTools.cli(VMFSTools.java:165)
    at com.fluidops.tools.vmfs.VMFSTools.main(VMFSTools.java:355)

Original comment by manasmu...@gmail.com on 24 Mar 2009 at 8:03

[GoogleCodeExporter]

If I understand it correctly, your VMFS spans two disk extents on two different 
LUNs.
This is a known shortcoming: disk extents are not supported yet by the driver.

Original comment by fluidops...@gmail.com on 26 Mar 2009 at 11:12

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi Ulrich,

Yes, your understanding is correct. I have gone through the code also, and 
figured 
out that the driver does not support it currently.

But, It would be really kind of you if you could help me on this. I mean, if 
you 
could give me any information (some header info or meta data info) which could 
help 
me make changes in the code and solve the issue.

As the driver is open source, I have already put in some efforts in going 
through the 
code and am now stuck with this issue. Any information on the headers or the 
manner 
in which the data is stored in the second LUN , will be really helpful.

Thanks,
Manas

Original comment by manasmu...@gmail.com on 26 Mar 2009 at 2:36

[GoogleCodeExporter]

The LUNs are managed with a Logical Volume Manager (LVM).
A first test would be to check compatibility and mount the 2 LUNs as a logical 
volume
from a reguar Linux system (using LVM tools). Then, the driver should be able 
to work
on the resulting logical volume like /dev/volg1/logv1.

For further steps, the on disk format, and source code of LVM can be found here:
http://sources.redhat.com/lvm/

-- Thanks

Original comment by fluidops...@gmail.com on 27 Mar 2009 at 10:40

[GoogleCodeExporter]

VMFS LVM with multiple extents is supported in r95.

Original comment by fluidops...@gmail.com on 26 Jan 2010 at 7:22

[GoogleCodeExporter]

Original comment by fluidops...@gmail.com on 26 Jan 2010 at 7:25

• Changed state: Fixed