Commit Snapshot failed VMFS timed out

[VCPMa]

Hello @all,

at the moment i have a big Problem with one VM.

I want to commit a Snapshot with the system but they runs into an error

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)WARNING: Helper: 1289: cancel request handle=1 fn=0x6140dc

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 772: Dumping non-active requests on HELPER_MISC_QUEUE at 26251006963731904

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 2: status=1 func=0x613fc4 since=26250680085076080

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 3: status=1 func=0x613c48 since=26250680592721424

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 4: status=1 func=0x612fd0 since=26250682911682808

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 5: status=1 func=0x618c24 since=26250684864642648

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 6: status=1 func=0x613c48 since=26250699953840400

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 7: status=1 func=0x613c48 since=26250703473107824

vmesx01 vmkernel: 113:22:22:56.177 cpu0:1024)Helper: 779: 8: status=1 func=0x618c24 since=26250704125464800

vmesx01 vmkernel: 113:22:23:30.586 cpu0:1024)VMNIX: VMFS: 247: timed out

hostd logs

867 'HostsvcPlugin' 77036464 warning] HostCtl error in GetRsrcSpec: SysinfoException: NodeId(619) ; Status(195887136)= Timeout; Message= Unable to get Int

961 'Vmomi' 77036464 info] Activation : Invoke done on

961 'Vmomi' 77036464 info] Throw vim.fault.PlatformConfigFault

971 'Vmomi' 77036464 info] Result

i use ESX 3.0.2

VC 2.0.2

Can somebody help me ??

Thanks

VCP Ma

[TomHowarth]

you could do a vmkfstool -i and clone the disk, this will commit the snapshot, once the clone has finished remap the VM to the new cloned disk and then delete the old one together with the snapshot delta, however even though you have received a timeout response it should still be running. just keep monitoring the delta file and you will see it shrinking. if you can shutdown the guest as this will speed up the commitment as well.

Tom Howarth

VMware Communities User Moderator

[VCPMa]

Hello Tom,

thaks for the answer.

i think the biggest Problem is the file size of the snapshot.

durin the last days on file server files was migrate onto the server with the snapshot, that are 190 GB.

Do you know how long does i need to create a clone ????

Regards

DaskTill

[TomHowarth]

ouch, 190Gb that could take weeks to commit.

it would definately be quicker to clone, if you can afford down time it's easier to do a cold clone. you could do a hot clone using Converter. I could not realy give estimate of the time needed but it would definately be considerablely quicker

Tom Howarth

VMware Communities User Moderator

[VCPMa]

argh....

weeks to commit the files, that is not possible.

Do you mean weeks by online commiting or by a cold clone???

can i use the command vmware-cmd *.vmx deletesnapshots

mayb, I think it will be better to take a full backup of the files,

delete the Disk,

create a new disk and make a restore from tape.

Regards

DaskTill

[TomHowarth]

No I meant weeks to commit the snapshot. this would be due to the fact that the delta file would be re-written each time peice was commtted, untill such a time as it was all in the VMDK, however new deltas would be being added to the snapshot at the same time as it was being committed.

this is why I recommended a cold Clone of the Guest, this would be quicker by an order of magnitude

Tom Howarth

VMware Communities User Moderator

[kastro]

The simpliest and probably fastest/safest way is to power off VM and clone it to new VM. This way you will end up with new VM without snapsots (they will be commited to new vmdk's). If you like you can then commit snapshot on original VM and wait (for a long time because 190G will need a lot of time to commit). Because task will probably timed out you can watch it with esxtop in SC if there is still trafic on HBA adapter. If something go wrong during commitmed you still have cloned VM.

[zemotard]

In all cases, never cancel a deletion, else you can have some data corruption.

If the deletion has been started, you must to wait the end of this deletion.

The timeout message appears after few minutes, but the deletion is still in progress

Regards

[TomHowarth]

as zemotard say do not kill the running commit process, once you have completed your cold clone of the guest and verified that all is in order by running it. then you can safely kill the commit process on the old Guest. and safely delete old machine and snap

Tom Howarth

VMware Communities User Moderator