StarWind Software

Hi, me again. You gonna get fed up with me

Ok, I just removed all my software firewalls to aviod any further problems.
(I'm behind a hardware NAT/SPI router so i'm OK for now).

I shared a HD (non SYSTEM or PAGEFILE) from the server (MARS) and connected from this machine (EARTH).
I could read and write without a problem.

Testing over, I went to StarPort to remove the device.
I got some error about the drive being in use.
OK, no problem there, something is still hanging onto it

But now the drive connection has gone from StarPort.
StarWind (on MARS) still shows an active connection from EARTH.
I cannot remove it from StarWind because it says it's in use!!!

I cannot re-add it to StarPort, I just get an error.
Bit of a catch 22 eh?

I got round the problem like this:

1) start CMD.EXE

Type NET STOP STARWINDSERVICE

(that gave an error but still stopped)

2) Edit the StarWind.conf file to remove the add device entry.

3) NET START STARWINDSERVICE.

Now It's all back to normal.

Not sure stopping the serivce is a good idea. Other shared devices would be lost together with hanging one... Valery, would you be so kind to check this issue? Thanks!

It's OK, I only had the one connection going at that time.

Tim,

We know about the issue with StarWind not closing a session. It happens rather rarely, but it seems there is a bug that leads to the problem.
We'll try to pin out and fix it in the nearest future.

As a work-around you could allow several sessions to the target. (for example -share:rw -sessions:2) or use an ImageFile target with -clustered:yes.
This will allow the initiator to log in the next time after a previous hanged disconnect...

OK, thanks.

Apart from some small problems, StarWind and StarPort really do rock!

Thank you very much for your remark! We would do our best to meet your expecations

P.S. And you should see new version of StarWind coming soon. A LOT of new features (including software RAID, volume snapshots, replication, Web UI etc etc etc). Hold on!

Tim wrote:OK, thanks.

Apart from some small problems, StarWind and StarPort really do rock!

I found that the problem also occurs if I reboot the initiator machine.

The StarWind target still shows a connection so when the StarPort machine reboots it cannot re-connect because that connection is in use.

As a work-around you could allow several sessions to the target. (for example -share:rw -sessions:2) or use an ImageFile target with -clustered:yes.

Instead in having to edit the CONF file you really need to put this stuff in the GUI.

Hi Tim,

The issue with not closing old sessions on reconnection has been reported by several people. We're working on it.
I think it will be fixed in a couple of days.

valery (staff) wrote:Hi Tim,

The issue with not closing old sessions on reconnection has been reported by several people. We're working on it.
I think it will be fixed in a couple of days.

Hi All,

I'd like to notify you that the problem with reconnection seems to be fixed in the recent release 2.6.4 build 20050901.

The only issue is using 2 different ISID values by the MS initiator, that could sometimes prevent reconnection if the old and the new ISIDs are not equal.

Yep, once again things are looking good.

I have been trying to break it but all seem OK.

Very good! I'd even say EXCELLENT!

Tim wrote:Yep, once again things are looking good.

I have been trying to break it but all seem OK.