Fiber target messed up

[rogerk]

Hi,

i have an similiar problem a year ago.
but with an Promise iscsi m610i.
after an power failure the time to connect to the LUN went up to 3-5 Minutes.
After that we noticed that the mapping was wrong on the initiator. on the promise it looks good.
all the data were corrupted.
we changed the management unit, with no effect. after changing the raidcontroller anythink was like as before. all the data were ok and so on...

so if you can change the raidcontroller, give it a chance.
what a raid controller you use for your DSS?

greetings
roger

[jmo]

Hi,

i have an similiar problem a year ago.
but with an Promise iscsi m610i.
after an power failure the time to connect to the LUN went up to 3-5 Minutes.
After that we noticed that the mapping was wrong on the initiator. on the promise it looks good.
all the data were corrupted.
we changed the management unit, with no effect. after changing the raidcontroller anythink was like as before. all the data were ok and so on...

so if you can change the raidcontroller, give it a chance.
what a raid controller you use for your DSS?

greetings
roger

Roger,

thank you for your feedback. We're using an Areca controller (16 port, I don't have the exact model number handy right now, I'm off-site until the end of the week).

I tend to believe we have a different situation here, but maybe that's just like whistling in the dark... The LUNs in themselves weren't messed up, even those FC groups where we had configured two LUNs where right - it was only that the wrong FC groups where "connected" to the FC initiators. That things had gone worse than expected was visible when two different Xen VMs (with differen WWPNs) were booting the same virtual disks - and that was the reason data got corrupted. (To be more precise: one VM was running, the second one started new on the Xen server - and came up with the same disks.)

After a simple DSS reboot everything went back to "normal" (in terms of group/initiator mapping).

With regards,
Jens