I have a physical Drive d:\Starwind_ISCSI with a 65GB image file, exported as Q: with 3 hyper-v vms. This has been working flawlessly for months.
I Upgraded to v8 beta on my workstation. On another physical drive f:\Starwind I create a 40GB LSFS container. Mounted it as R:
First thing i go to do is copy one VM 30GB from Q: to R: All looks good for first few mins, copying at around 90MB/sec. ABout half way through file copy, speeds fluctuate. OK could be caused by many things.. Near 90% of the file copy, speed goes to 0 bytes/sec. I left it for 10 mins, no change.
Event log filling with "Target did not respond in time for a SCSI request. The CDB is given in the dump data."
Ended up having to reboot..
On next boot I delete the new 40GB LSFS container and target.
I copy the 3 Hyper-V VMs from iSCSI Q: to physical f:\
Now make a new LSFS container 40GB. Mounted as R: again.
Copy from F: one of the VMs 30GB to new R:
Again, failed at just over 90%.
EventLog:
A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.
Target did not respond in time for a SCSI request. The CDB is given in the dump data.
Target did not respond in time for a SCSI request. The CDB is given in the dump data.
Target did not respond in time for a SCSI request. The CDB is given in the dump data.
...
- SW-v8-A.JPG (192.57 KiB) Viewed 30740 times
Should I post logfiles, or just wait for next beta?
Brian
