Dear Community,
i am working with Starwind Software for a few Month now and sofar everything has worked fine. I use Starwind on a iSCSI-SAN in a VMware ESX3.x environment without any Problems up to now. I have setup 2 * 160 GB Drives as Bridge Devices to the ESX Servers and they contain vmfs3 Filestructure to contain Virtual Machine Files. Last week i have replaced one of the 160GB Bridged Disks with a 500 GB Disk. All went ok, after several reboots/rescans it appeared correctly in my ESX Environment. Write operations to the new iSCSI Target (500GB) was also ok, but reading a lot of Data caused the Starwind Server to hang and no more I/O was possible. After this i have removed everything again and put it in my Testenvironment (I should have done that in the first place)
This is what came out after a 3 day testing and experimenting period:
Any Disk Bridge (and imagefile) iSCSI Targets, where the Disk itself is greater then 160GB, caused Starwind Server Hangs. (No Logfilereading anymore possible, also no Entries after reboot)
ESX Server Log reports ScsiPath Timeouts
The Starwind Server ends up on 100% CPU Load, (Hardware Interrupts), no more interaction possible.
As mentioned above, this only happens on Disks greater then 160GB, with 160GB or smaller Disks all is ok. Also creating an imagefile instead of a Bridge does not change anything.
Anyone has an idea or similar experience,
thanks and regards
Harry
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software