Got below error while trying to combine snapshot files.
vmkfstools -i AXTST167-000001.vmdk /vmfs/volumes/datastore1/axtstbundled/AXTST167.vmdk
Destination disk format: VMFS zeroedthick
Failed to open 'AXTST167-000001.vmdk': Invalid argument (1441801).
are you trying with vm powered off or powered on?
please post the file '/vmfs/volumes/datastore1/axtst167/AXTST167-000001.vmdk
it may be invalid or use a dead link
Although the error message mentions the source disk, please verify whether the destination folder "axtstbundled" already exist? If not you need to create it manually.
André
Yes I tried with Powered off.
I have already created folder as you can seen below... Attached my vmdk file output.
its a descriptor file and you are trying to clone a descriptor file, it will not happen. cloning can be done for flat files. If you are really interested in having another copy of your AXTST167-000001.vmdk file then use cp command for it, vmkfstool wont work for it and there is no thin or thick format for descriptor file, infact you would be providing info for thin or thick inside ur descriptor to which its pointing.
Sorry, but this is not quite correct. vmkfstools only accepts the descriptor file names as arguments, as they contain the disk's metadata as well as the name of the flat and/or delta .vmdk files.
André
WOH, I got confused and I have given a try in my lab to confirm and YES. I almost forgot that this is the thread even I commented earlier.
@Thread initiator: Have you ever tried to expand the size of the disk when it had snapshot??
please check the below link,
No I didnt try doing that one.
Please check below for vmkfstools with verbose log
PETERMULE wrote:
No I didnt try doing that one.
Please check below for vmkfstools with verbose log
/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167 # vmkfstools -i AXTST167-000001.vmdk NEEWWWWWW.vmdk -v 10DISKLIB-VMFS : "./AXTST167-000001-delta.vmdk" : open successful (285) size = 250081413120, hd = 0. Type 8DISKLIB-VMFS : "./AXTST167-000001-delta.vmdk" : closed.Destination disk format: VMFS zeroedthickDISKLIB-VMFS : "./AXTST167-000001-delta.vmdk" : open successful (14) size = 72696156160, hd = 4621068. Type 8DISKLIB-DSCPTR: Opened [0]: "AXTST167-000001-delta.vmdk" (0xe)DISKLIB-LINK : Opened 'AXTST167-000001.vmdk' (0xe): vmfsSparse, 488440260 sectors / 232.9 GB.DISKLIB-VMFS : "/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167/AXTST167-flat.vmdk" : open successful (14) size = 250081413120, hd = 4031245. Type 3DISKLIB-DSCPTR: Opened [0]: "AXTST167-flat.vmdk" (0xe)DISKLIB-LINK : Opened '/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167/AXTST167.vmdk' (0xe): vmfs, 488440260 sectors / 232.9 GB.DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1DISKLIB-CHAINESX : ChainESXOpenSubChainNode: can't create deltadisk node 7fd40f53-AXTST167-000001-delta.vmdk failed with error Invalid argument (0xbad0007, Bad parameter)DISKLIB-CHAIN : "AXTST167-000001.vmdk" : failed to open (Invalid argument).DISKLIB-VMFS : "./AXTST167-000001-delta.vmdk" : closed.DISKLIB-VMFS : "/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167/AXTST167-flat.vmdk" : closed.DISKLIB-LIB : Failed to open 'AXTST167-000001.vmdk' with flags 0xe Invalid argument (1441801).Failed to open 'AXTST167-000001.vmdk': Invalid argument (1441801)./vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167 #is the CID's broken?
check with this and post the results
vmkfstools -q AXTST167-000001.vmdk
Have checked for CID it is correct.
the error says there is no issue with CID.
PETERMULE wrote:
Have checked for CID it is correct.
Getting following error while running this command/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167 # vmkfstools -q AXTST167-000001.vmdkAXTST167-000001.vmdk is not an rdmnow, you have some vmdk file missing,
run this in verbose and check the o/p
vmkfstools -q AXTST167-000001.vmdk -v 10
this is fine as well, you don't have any missing vmdk which is a god news. Now, what is the space available in your datastore?
I have got 425.6 GB available in Datastore
I have got 465 GB available in datastore
Filesystem Size Used Available Use% Mounted on
visorfs 1.3G 262.8M 1.0G 20% /
vfat 4.0G 3.3M 4.0G 0% /vmfs/volumes/4d5ea70a-ec835c01-b652-e0699500dd1f
vmfs3 926.5G 500.9G 425.6G 54% /vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f
vfat 249.7M 89.2M 160.5M 36% /vmfs/volumes/cb7dad7b-76399004-85ea-7acdb59dd4d2
vfat 249.7M 4.0k 249.7M 0% /vmfs/volumes/ae3cb87a-3213faf8-783c-152ab3b1199e
vfat 285.9M 140.7M 145.2M 49% /vmfs/volumes/2da668ef-40e5d96b-90bf-855ddb9c5547
can you try this
After doing all that Iam still getting the same error.