DSS6.0up10 Replication problem I/O errors

[eppo78]

try using LUN 1
in esx 3.5 it did not like lun 0

Are you replicating through the Qlogic QLE2462?
if not what type of nic are you using

I don't think it is ESX related as I have the same problem with a empty volume without a LUN assigned to it.

As far as I know you can only replicate through a nic ( Intel 82575EB internal)
Thanks for you reply though.

Eddo

[eppo78]

The same issue occurs while replicating a 500GB volume...

[symm]

Did you try sending the logs to support?

did the initilization finish before you started the replication ?


BTW it does not seem like a vmware issue, but here is a link to the post concerning LUN 0

http://kb.vmware.com/selfservice/mic...8601&stateId=0 0 44972208

[eppo78]

I did wait until initilization finished, I even waited to put data on it until the initial replication would finish, but it never does.

Thanks for the LUN 0 info.

[eppo78]

I always send my logfiles with the mails I send to support. I'm still waiting for an anwser...

[symm]

keep us updated with your progress

[JFleck]

You are not alone with this issue. I've also submitted a ticket and am awaiting a reply. I have two devices that I believe are identical in hardware and software. Replication from device A to Device B seems to be working without a problem. However, Replication from Device B to Device A seems to fail and cause both units to hang and reports a Journal committ error. fortunately I haven't lost any data, but it does require a hard power cycle (reboot command from console doesn't seem to do it) and it trashes any of the replications that I did have. I am using the default 40mb for my replication tasks.