:eek:
Is this correct behaviour? I have two vms running from our iscsi storage. When i create a new iscsi volume all my vm machines hang until the initialize has finished !!
This is obviously not goo in a production environment. Should it do this?
Printable View
:eek:
Is this correct behaviour? I have two vms running from our iscsi storage. When i create a new iscsi volume all my vm machines hang until the initialize has finished !!
This is obviously not goo in a production environment. Should it do this?
This is a well known issue and a soon to be released version of DSS 6 (in beta now) will allow you to set the performance of how much cpu to use when initializing file i/o volumes. If you need it right away you might put in a support request or check the forums for the version (4.1.something) which I think is available via ftp.
Actually build up14 B4221 is released already (at least on the ftp server)
My advices is to would stick with Block I/O. The init process will take a very long time if you set it to levels that do not cause this behavior. Especially if you are using large volumes. I can't wait 2 days for a 2TB volume to init. At the same time, I can't break my network because I want it to init faster. BTW, Kudos to Open-e for finally getting this in the product.
There is always a lot of talk about File IO being faster for VMWare, but I think your mileage will vary. I have used both File io and block IO and I can't tell the difference.