vmkfstools doesn't use default output filename

[osde_info]

I can't import vmdks to .

This doesn't work

1. cd /vmfs/volumes/storage/myvm

1. vmkfstools -i /vmimages/vmbk/vm-cerb3/cerberus-0.3.0-x86.vmdk .

This does work

1. cd /vmfs/volumes/storage/myvm

1. vmkfstools -i /vmimages/vmbk/vm-cerb3/cerberus-0.3.0-x86.vmdk cerberus-0.3.0-x86.vmdk

regards

clive (aka osde.info)

[oreeh]

The man page doesn't state that you can omit the destination argument.

[osde_info]

i don't consider puting a "." as "ommiting a destination" btw it also fails if you only specify a destination directory/

1. vmkfstools -i /vmimages/vmbk/vm-r2testwinda/OS.vmdk w2k3r2a/ (with or without final/)

Destination disk format: VMFS thick

Cloning disk '/vmimages/vmbk/vm-r2testwinda/OS.vmdk'...

Failed to clone disk : The file already exists. (39)

I think the error message is misleading too since the file DOESN'T exist since i am trying to create (import) it !

regards

clive (aka osde.info)

[oreeh]

i don't consider puting a "." as "ommiting a destination"

Since the dot actually represents the current folder it is an invalid destination (you surely don't want to overwrite the current folder).

btw it also fails if you only specify a destination directory/

This is the same as specifying a dot

The man page states that you have to specify a disk name as the destination.

[osde_info]

i guess vmkftools just has differnent behaviour to the UNIX cp command !

regards

clive (aka osde.info)

[sbeaver · Accepted solution]

Yes exactly CP and VMKFSTOOLS are completely different beasts in every way

Steve Beaver

VMTN Forum Moderator

*Virtualization is a journey, not a project.*