PETERMULE
Contributor
Contributor

Unable to combine Snapshot file with Flat file

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).

vmkfstools -i /vmfs/volumes/datastore1/axtst167/AXTST167-000001.vmdk -d thin /vmfs/volumes/datastore1/axtstbundled/AXTST167_NEWW.vmdk
Destination disk format: VMFS thin-provisioned
Failed to open '/vmfs/volumes/datastore1/axtst167/AXTST167-000001.vmdk': Invalid argument (1441801).
0 Kudos
33 Replies

are you trying with vm powered off or powered on?

Regards, ABFS
0 Kudos
continuum
Immortal
Immortal

please post the file '/vmfs/volumes/datastore1/axtst167/AXTST167-000001.vmdk

it may be invalid or use a dead link


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
a_p_
Leadership
Leadership

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é

0 Kudos
PETERMULE
Contributor
Contributor

Yes I tried with Powered off.

0 Kudos
PETERMULE
Contributor
Contributor

I have already created folder as you can seen below... Attached my vmdk file output.

/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f # cd axtstbundled
/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/axtstbundled # ls
/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/axtstbundled # pwd
/vmfs/volumes/datastore1/axtstbundled
/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/axtstbundled #
/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/axtstbundled # cat /vmfs/volumes/datastore1/axtst167/AXTST167-000001.vmdk
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=6269d823
parentCID=6dbed603
isNativeSnapshot="no"
createType="vmfsSparse"
parentFileNameHint="AXTST167.vmdk"
# Extent description
RW 488440260 VMFSSPARSE "AXTST167-000001-delta.vmdk"
# The Disk Data Base
#DDB
ddb.toolsVersion = "0"
ddb.longContentID = "78bde9f2e719d58fcc5ae3a26269d823"
/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/axtstbundled #
0 Kudos

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.

Regards, ABFS
0 Kudos
a_p_
Leadership
Leadership

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é

0 Kudos

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,

http://geosub.es/vmutils/Troubleshooting.Virtual.Machine.snapshot.problems/Troubleshooting.Virtual.M...

Regards, ABFS
0 Kudos
PETERMULE
Contributor
Contributor

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 10
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : open successful (285) size = 250081413120, hd = 0. Type 8
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : closed.
Destination disk format: VMFS zeroedthick
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : open successful (14) size = 72696156160, hd = 4621068. Type 8
DISKLIB-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 3
DISKLIB-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 = 1
DISKLIB-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 #
0 Kudos

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 10
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : open successful (285) size = 250081413120, hd = 0. Type 8
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : closed.
Destination disk format: VMFS zeroedthick
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : open successful (14) size = 72696156160, hd = 4621068. Type 8
DISKLIB-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 3
DISKLIB-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 = 1
DISKLIB-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

Regards, ABFS
0 Kudos
PETERMULE
Contributor
Contributor

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.vmdk
AXTST167-000001.vmdk is not an rdm
0 Kudos

the error says there is no issue with CID.

Regards, ABFS
0 Kudos

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.vmdk
AXTST167-000001.vmdk is not an rdm

now, you have some vmdk file missing,

run this in verbose and check the o/p

vmkfstools -q AXTST167-000001.vmdk -v 10

Regards, ABFS
0 Kudos
PETERMULE
Contributor
Contributor

/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167 # vmkfstools -q AXTST167-000001.vmdk -v 10
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : open successful (23) size = 250081413120, hd = 0. Type 8
DISKLIB-VMFS  : "/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167/AXTST167-flat.vmdk" : open successful (23) size = 250081413120, hd = 0. Type 3
AXTST167-000001.vmdk is not an rdm
DISKLIB-VMFS  : "./AXTST167-000001-delta.vmdk" : closed.
DISKLIB-VMFS  : "/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/NEW_AXTST167/AXTST167-flat.vmdk" : closed.
AIOMGR-S : stat o=2 r=6 w=0 i=0 br=98304 bw=0
0 Kudos

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?

Regards, ABFS
0 Kudos
PETERMULE
Contributor
Contributor

I have got 425.6 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
0 Kudos
PETERMULE
Contributor
Contributor

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

0 Kudos

0 Kudos
PETERMULE
Contributor
Contributor

After doing all that Iam still getting the same error.

Reason: 22 (Invalid argument).
Cannot open the disk '/vmfs/volumes/4d5ea70e-f965c886-3e79-e0699500dd1f/AXTST167_/AAXTST167-000001.vmdk' or one of the snapshot disks it depends on.
0 Kudos