Unsolved
This post is more than 5 years old
10 Posts
0
670
September 8th, 2017 10:00
VNX FF_ASSERT_PANIC and how VMs reacted
A couple of nights ago I had the dubious honor of experiencing a FF_ASSERT_PANIC on my VNX5700. Both SP's rebooted at roughly the same time.
This array mostly services VMWare ESX. None of the ESX servers themselves were phased, but there was a vast difference in how Linux VM's reacted vs. how Windows VMs reacted.
Amazingly enough, only ONE Windows VM was affected. The rest weathered the storm unphased.
Conversely, ALL 400+ Linux VMs went into "read only" mode and had to be rebooted. These VMs are almost exclusively RHEL6, with a few other distributions mixed in.
Any insight into why the Windows VMs were fine (unexpected) and the Linux VMs all got stupid (unexpected)?



rewalmilo
1 Rookie
•
62 Posts
0
September 11th, 2017 03:00
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009465#.V7WFQy3gSSo.email
coud be some thing like this. Linux I/O time out. Check this VMware KB