I tried your values.

The size of the Logfile grows in 1 hour to 78 MB.
with loglevel 2 it grows in 1 hour to 146 MB.

In my opinion this ist much to big.

I changed it manually.

i found it on this topic.

http://www.starwindsoftware.com/forums/ ... hlight=log

but why is the verbose loglevel and not disabled ?????

<!--LogLevel values: 0-Disabled, 1-Errors, 2-Warnings, 3-all messages -->

My configuration 2 ESX Server 2 mirrored Starwind server Mirror Source Device: Mirror0 (esxsan1) Image file name: Mirror Volumes\D\iSCSI Volumes\esxsan1.mir Total size: 4016 MB First image path: D:\iSCSI Volumes\esxsan1.img (active) First image state: Valid Second image path: #iscsi:192.168.1.52:326...

Hi, i´ve got a Problem with my Logfile it grows and grows and grows until there is no free space left on my Harddisk. At least it grows to about 12GB in less than one week. In the Starwind.cfg i made the following changes: <logging> <!--LogLevel values: 0-Disabled, 1-Errors, 2-Warnings, 3-all messa...

Hi bohdan,

thank you for your very fast response.

With the new versions this issue is solved.

Thanks

Hi bohdan,

I have the following versions of your software.

StarWind iSCSI Target v3.5.3 (Build 20080225, Win32)

StarPort v.3.5.4 (Build 0x20080111)
StarPort Driver Version 0x00030001

What are the latest builds?

Thanks

Yesterday i tried to to get the starwind iscsi target to work with replication. Therefore i installed 2 vmware machines 2003 Server to see how the things work. And i got exactly the same error message as GTB. I successfully connected to the iscsi target manually with starport. 3/11 10:31:52.984 c68 ...