• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Problem post ovf crater

D

defuseme2k

[H]ard|Gawd
Joined
Oct 7, 2004
Messages
1,074
So I had an OVF import go south, my laptop here at work decided to be stupid while letting this thing run... so long story short my connection dropped and the import busted.

Not that big of a deal, except I cannot delete the folder that it was importing to. There is one file in there... a -flat.vmdk which reports as being busy when trying to delete from the command line. The thing is, I run a vmkfstools -D and get the UUID of the owner out of the vmkernel log... well, it doesn't match ANY of my host's UUIDs (pumped from esxcfg-info) ... wtf! I've never seen that? I have not yet bounced the hosts or restarted agents. You gotta realize that is a nightmare at this scale, so I really need to track it down.

Any ideas, especially YOU lopoetve?
 
I can't take the credit alone, but this is sorted out. I'm in an oddball situation where calling VMware for support isn't an option and the vendor who provides it is a joke. SO I'm left to my own vices. First I had to troll a ton of logs and finally figured out which host the ovf import was working its way through. Then a simple restart of vpxa fixed it. I had some Linux gurus around here helping me, but ultimately I figured it out. They deserve some kind of a shout out for spending so much time on it with me :).

*sigh* I still don't get why the UUID when I ran vmkfstools -D didn't match? Is this because it was vpxa instead of hostd? Anyone know?
 
Local UUID. What were you checking vmkfstools -D against, anyway? IT should be vmkernel ID, which is found with: esxcfg-info.
 
lopoetve said:
Local UUID. What were you checking vmkfstools -D against, anyway? IT should be vmkernel ID, which is found with: esxcfg-info.
Click to expand...

There was a -flat.vmdk I couldn't delete, I was running it against that trying to figure out which host was owning. And yes, that is what i'm saying. I ran it vmkfstools -D against it and then ran esxcfg-info. None of the hosts UUIDs matched. That is why I'm asking, because the ovf import seems to work a bit oddly anyway; I was curious if it was being imported in a way where the UUID wouldn't match.
 
Well, it'll probably have been the "uuid" of the host sending it data, through VPXA, or a local lock which is relatively nonsensical in terms of translating.
 
You must log in or register to reply here.
Back
Top