Page 2 of 2

Re: Disk Bridging Bug Report

Posted: Sun Mar 02, 2014 2:51 am
by AKnowles
Just a quick update on the new RC build on disk bridging. I upgraded my current build after deleting the LUNs. I rebuilt my think, thin, and SSD (disk bridge) to test the behavior against the previous build. The disk bridging killed Starwind. Hung up the RPC Server so I couldn't do much of anything with the Computer Manager. The Starwind console could not connect to the service either.

I managed to recover the situation by stopping the Starwind service, using diskpart to select the SSD, clean the SSD, then take it ofline, and finally restart the Starwind service. I'll post the original log, but will try a few more clean boots and options this weekend if possible.

Re: Disk Bridging Bug Report

Posted: Sun Mar 02, 2014 12:00 pm
by anton (staff)
Nice... Thank you for reporting we'll check this out!

Re: Disk Bridging Bug Report

Posted: Mon Mar 03, 2014 11:07 am
by Alex (staff)
AKnowles,
Could you please send us also the previous log file? StarWind service starts new log file after each restart, so I assume, all the interesting records are there.
Current file contains records starting from 3/1 18:08:27.854 .

Re: Disk Bridging Bug Report

Posted: Mon Mar 03, 2014 4:22 pm
by AKnowles
The file is too large. Compress it is a bit over two MB. Can I e-mail it or post it elsewhere for you?

Re: Disk Bridging Bug Report

Posted: Mon Mar 03, 2014 4:38 pm
by Anatoly (staff)
Exactly! You can compress it and drop it to me: av@starwind.com
Please note that if the archive will be larger then 10MBs you`ll it will not pass our mail filters, so it will be better to upload it to some file hosting service (GDrive, DropBox, etc) and share the link with community or with me personally, after. Please don`t forget to put the reference to this thread if you`ll send me the email.

Thank you

Re: Disk Bridging Bug Report

Posted: Mon Mar 03, 2014 4:46 pm
by AKnowles
It is on the way.

Re: Disk Bridging Bug Report

Posted: Mon Mar 03, 2014 9:31 pm
by anton (staff)
Thank you! We'll take a look as soon as we'll get the stuff :)

Re: Disk Bridging Bug Report

Posted: Thu Mar 06, 2014 3:28 pm
by Alex (staff)
AKnowles,
We have reviewed the logs. The only wrong thing in logs is error on locking the volumes of SSD storage.
When DiskBridge opens device, it tries to lock volumes that reside on this device. This is needed to exclude possibility of simultaneous access to disk volumes from server' OS and from client that have access to this disk via iSCSI. When disk volumes are in use on the server, StarWind fails to lock the disk and returns error to iSCSI initiator that connects to the target.

One thing - we have tried this in our lab and it works as expected: Initiator hangs up for several seconds and displays error. Server processes connection from Management Console and from other targets without errors.

Have you faced the same issue again after the first time? Is it easy to reproduce the issue on your server?

Re: Disk Bridging Bug Report

Posted: Thu Mar 06, 2014 5:06 pm
by AKnowles
I haven't had a chance to try it again as I have been studying for my VCAP-DCA exam on Saturday, but I will try a few things on Sunday to see what happens.

Re: Disk Bridging Bug Report

Posted: Thu Mar 06, 2014 5:15 pm
by Alex (staff)
Thank you!

Re: Disk Bridging Bug Report

Posted: Mon Mar 24, 2014 5:49 pm
by AKnowles
Anton,

Just a follow up. I'm still having an issue with disk bridging. Almost the same issue as previously. I was able to create the disk bridge without taking the disk offline. But then ESXi 5.5 could not format it with the previous GPT partition. So, after taking it offline, cleaning it, then reattaching it to Starwind RC1 I could present it to ESXi 5.5, but it would not format it (different error). Even after a reboot of the ESXi hosts and the Starwind Server it could not be formatted.

I'm going to try and start with a clean slate on it and see if that work. In the meantime, here's my log from my attempts ...

Re: Disk Bridging Bug Report

Posted: Fri Mar 28, 2014 4:51 pm
by Alex (staff)
I have reviewed the logs. Every write attempt ends with "The media is write-protected." error (code 19).
Could you please show also Windows Event log records? May be, there we'll find some clues to issues with locking device for read-write access.

Re: Disk Bridging Bug Report

Posted: Sun Apr 06, 2014 3:36 am
by AKnowles
Alex,

I will purge both teh Windows & Starwind logs, reboot, and try and replicate the event and provide both sets of logs to you.

Thnaks,

Art

Re: Disk Bridging Bug Report

Posted: Tue May 06, 2014 10:40 pm
by AKnowles
Just an update. I used the latest build and can once again create a disk bridge. But it only worked when I cleaned the disk (removed all partitions) and left the disk online. In prior builds it needed to be offline. I'm not sure if this is a quirk of Windows Server 2012 R2 or not. I'll see if I can do a bit more testing on the weekend, but I was happy to just be able to mount it once again.

Re: Disk Bridging Bug Report

Posted: Tue May 06, 2014 10:56 pm
by anton (staff)
Various "issues" like this is one of the reasons say MSFT had ripped this functionality off their target...
AKnowles wrote:Just an update. I used the latest build and can once again create a disk bridge. But it only worked when I cleaned the disk (removed all partitions) and left the disk online. In prior builds it needed to be offline. I'm not sure if this is a quirk of Windows Server 2012 R2 or not. I'll see if I can do a bit more testing on the weekend, but I was happy to just be able to mount it once again.