Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
|
ESX/ESXi 4.x host fails with a purple diagnostic screen when VMFS snapshot volumes are exposed to multiple hosts in a vCenter Server cluster (2007353)
Symptoms
- ESX/ESXi 4.x host fails with a purple diagnostic screen
- In the vmkdump file or the purple diagnostic screen, you see entries similar to:
0:19:06:35.786 cpu6:4109)LVM: 2399: [naa.60060e80104527d004f2a62d00000024:1] devID mismatch:
0:19:06:35.786 cpu6:4109)LVM: 2400: Cached: <naa.60060e80104527d004f2a62d00000024:1>
0:19:06:35.786 cpu6:4109)LVM: 2402: Read: 4c61a522-f99b5167-0d1a-001d09f2d60b
0:19:06:35.786 cpu7:4111)DevFS: 2370: Unable to find device: 4bba7f1b-80e79a08-11a9-0023aef8c1c2
0:19:06:35.786 cpu7:4111)WARNING: LVM: 8703: arrIdx (1024) out of bounds
0:19:06:35.845 cpu6:4109)LVM: 7165: Device naa.60060e80104527d004f2a62d00000027:1 detected to be a snapshot:
0:19:06:35.845 cpu6:4109)LVM: 7172: queried disk ID: <type 2, len 22, lun 39, devType 0, scsi 0, h(id) 6763519106745717545>
0:19:06:35.845 cpu6:4109)LVM: 7179: on-disk disk ID: <type 2, len 22, lun 39, devType 0, scsi 5, h(id) 17822744141607108003>
VMware ESX [Releasebuild-261974 X86_64]
#PF Exception(14) in world 4109:helper1-0 ip 0x418029d04c6b addr 0xffffffffffffffcc
LBR: from 0x418029d0555b to 0x418029d04c54
cr2=0xffffffffffffffcc cr3=0x400eb000 cr4=0x16c
frame=0x4100c006f6c8 ip=0x418029d04c6b err=0 rflags=0x10283
rax=0x14 rbx=0x4100b1802f20 rcx=0x14
rdx=0x4100c006fb90 rbp=0x4100c006f850 rsi=0xffffffffffffffcc
rdi=0x4100b180c7a4 r8=0xffffffffffffff78 r9=0x4100b180c7a4
r10=0x417feab90320 r11=0x0 r12=0x4100b180c7a4
r13=0x4100b180c750 r14=0x4100b1802cd0 r15=0x4100b184e610
0:4096/console 1:4253/net-cdp 2:4098/idle2 3:4099/idle3
4:4100/idle4 5:4101/idle5 *6:4109/helper1-0 7:4103/idle7
@BlueScreen: #PF Exception(14) in world 4109:helper1-0 ip 0x418029d04c6b addr 0xffffffffffffffcc
LBR: from 0x418029d0555b to 0x418029d04c54
Code starts at 0x418029800000
0x4100c006f850:[0x418029d04c6b]LVMUpdateVolume+0x2c2 stack: 0x4100c006fa5f
0x4100c006fa90:[0x418029cffbc0]LVMDoForEachVolume+0x19b stack: 0x417fe9819cc0
0x4100c006fbd0:[0x418029d019b8]LVMProbeDeviceInt+0x50b stack: 0x4100c006fc10
0x4100c006fc40:[0x418029d02ee8]LVM_Probe+0x33 stack: 0x417fe9819cc0
0x4100c006fc80:[0x418029d02fcc]LVM_ProbeWithRetry+0x2f stack: 0x0
0x4100c006fcd0:[0x418029a019bb]FDS_RescanDevices+0x322 stack: 0x410001005b20
0x4100c006fe40:[0x4180299fa66f]VC_RescanVolumes+0xee stack: 0x368
0x4100c006fe60:[0x4180299fa968]SystemVsi_VmfsOnlyVCScanSet+0x27 stack: 0x4100c006fed0
0x4100c006fee0:[0x418029a9f649]VSI_SetInfo+0x100 stack: 0x4100000000a0
0x4100c006ff50:[0x4180298a30e3]HostVSISetInfoWrapper+0x92 stack: 0x4100000000a0
0x4100c006ff80:[0x4180298af155]VMNIXVMKSyscallUnpackVSI_Set_HelpFn+0x44 stack: 0x0
0x4100c006fff0:[0x418029864d1b]helpFunc+0x4c2 stack: 0x0
0x4100c006fff8:[0x0]Unknown stack: 0x0
VMK uptime: 0:19:06:35.865 TSC: 160122162648147
FSbase (0x0) GSbase (0x0) kernelGSbase (0x0)
Starting coredump to disk.
Dumping using slot 1 of 1... - An alternative purple screen or backtrace may be displayed with this issue:
ESC[7m246:09:41:42.102 cpu14:4120)WARNING: LVM: 9023: arrIdx (1024) out of bounds
ESC[0m 246:09:41:45.426 cpu3:4119)Backtrace for current CPU #3, worldID=4119, ebp=0x417f800bf748 246:09:41:45.427
cpu3:4119)0x417f800bf748:[0x4180378556a5]PanicLogBacktrace@vmkernel:nover+0x18 stack: 0x4180379d3d68, 0x417f8 246:09:41:45.427
cpu3:4119)0x417f800bf888:[0x4180378558e4]PanicvPanicInt@vmkernel:nover+0x1ab stack: 0x3000000010, 0x417f800bf 246:09:41:45.428
cpu3:4119)0x417f800bf968:[0x418037855d66]Panic_ExceptionMsg@vmkernel:nover+0xa5 stack: 0x418037e63b9e, 0x1f04 246:09:41:45.428
cpu3:4119)0x417f800bfa68:[0x418037855dec]Panic_Exception@vmkernel:nover+0x83 stack: 0x4100b2f06110, 0x4100bfc 246:09:41:45.429
cpu3:4119)0x417f800bfab8:[0x41803782dd81]IDTReturnPrepare@vmkernel:nover+0x254 stack: 0x417f800bfbe0, 0x41803 246:09:41:45.429
cpu3:4119)0x417f800bfac8:[0x4180378ded77]gate_entry@vmkernel:nover+0x46 stack: 0x4018, 0x4018, 0x1f0401, 0x0, 246:09:41:45.430
cpu3:4119)0x417f800bfbe0:[0x418037e63b9e]LVMDoForEachSnapVolume@esx:nover+0xa5 stack: 0x417ff852ddc0, 0xaffff 246:09:41:45.430
cpu3:4119)0x417f800bfc10:[0x418037e67262]LVMAutoResignatureOrMount@esx:nover+0xdd stack: 0x0, 0x417f800bfdf0, 246:09:41:45.430
cpu3:4119)0x417f800bfc70:[0x418037e687b7]LVM_EndRescan@esx:nover+0x1e2 stack: 0x0, 0x1, 0x417ff82bb700, 0x0, 246:09:41:45.431
cpu3:4119)0x417f800bfcc0:[0x418037a362b1]FDS_RescanDevices@vmkernel:nover+0x3c8 stack: 0x410006e25f60, 0x417f 246:09:41:45.431
cpu3:4119)0x417f800bfe30:[0x418037a2eaf4]VC_RescanVolumes@vmkernel:nover+0xef stack: 0x0, 0x100000001, 0x417f 246:09:41:45.432
cpu3:4119)0x417f800bfe50:[0x418037a2ee24]SystemVsi_VmfsOnlyVCScanSet@vmkernel:nover+0x27 stack: 0x417f800bff6 246:09:41:45.432
cpu3:4119)0x417f800bfee0:[0x418037af1e74]VSI_SetInfo@vmkernel:nover+0x17b stack: 0x417ff85adb20, 0x2c0, 0x0, 246:09:41:45.433
cpu3:4119)0x417f800bff60:[0x41803782d1de]HostVSISetInfoWrapper@vmkernel:nover+0xbd stack: 0x417ff85adb20, 0x4 246:09:41:45.433
cpu3:4119)0x417f800bff90:[0x4180378b4d7e]VMNIXVMKSyscallUnpackVSI_Set_HelpFn@vmkernel:nover+0x4d stack: 0x417 246:09:41:45.434
cpu3:4119)0x417f800bfff0:[0x4180378299ea]helpFunc@vmkernel:nover+0x501 stack: 0x0, 0x0, 0x0, 0x0, 0x0 246:09:41:45.434
cpu3:4119)0x417f800bfff8:[0x0]<unknown> stack: 0x0, 0x0, 0x0, 0x0, 0x0 246:09:41:45.435 cpu3:4119)ESC[45mESC[33;1m
VMware ESX 4.1.0 [Releasebuild-433742 X86_64]ESC[0m 246:09:41:45.435 cpu3:4119)
#PF Exception 14 in world 4119:helper1-1 IP 0x418037e63b9e addr 0x1f0409 246:09:41:45.435
cpu3:4119)cr0=0x80010039 cr2=0x1f0409 cr3=0x4008b000 cr4=0x16c 246:09:41:45.435
cpu3:4119)frame=0x417f800bfad8 ip=0x418037e63b9e err=0 rflags=0x10293 246:09:41:45.435
cpu3:4119)rax=0x1f0401 rbx=0x417f800bfdf0 rcx=0x0 246:09:41:45.435
cpu3:4119)rdx=0x4100b9482bc0 rbp=0x417f800bfbe0 rsi=0x4100b9482c48 246:09:41:45.435
cpu3:4119)rdi=0x4100bfe2f960 r8=0x148 r9=0x4100bfe2f900 246:09:41:45.435
cpu3:4119)r10=0x4100b2f01e38 r11=0x4100bfe2fa50 r12=0x0 246:09:41:45.435
cpu3:4119)r13=0x4100bfe2f910 r14=0x4100b9482db8 r15=0x1 246:09:41:45.435
cpu3:4119)pcpu:0 world:4112 name:"idle0" (I) 246:09:41:45.435
cpu3:4119)pcpu:1 world:4097 name:"idle1" (I) 246:09:41:45.435
cpu3:4119)pcpu:2 world:4098 name:"idle2" (I) 246:09:41:45.435
cpu3:4119)pcpu:3 world:4119 name:"helper1-1" (S) 246:09:41:45.435
cpu3:4119)pcpu:4 world:4100 name:"idle4" (I) 246:09:41:45.435
cpu3:4119)pcpu:5 world:4101 name:"idle5" (I) 246:09:41:45.435
cpu3:4119)pcpu:6 world:4102 name:"idle6" (I) 246:09:41:45.435
cpu3:4119)pcpu:7 world:22014 name:"vmm1:atlcmsindexer01" (V) 246:09:41:45.435
cpu3:4119)pcpu:8 world:4104 name:"idle8" (I) 246:09:41:45.435
cpu3:4119)pcpu:9 world:44511 name:"vmm0:atlctxtest" (V) 246:09:41:45.435
cpu3:4119)pcpu:10 world:4106 name:"idle10" (I) 246:09:
Resolution
This issue is resolved in ESX/ESXi 4.0 Update 3 and ESX/ESXi 4.1 Update 2.
To download these updates, see the VMware Download Center.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):