IO error issues with MD3000i on Linux

[Bryan]

It matters what hosts can access a lun since without something in the
OS to control file locking there is a high probability of eventually
corrupting your data.

On 6/14/09, Morten W. Petersen <morten at nidelven-it.no> wrote:
> Matthew Geier skrev:
>> morten at nidelven-it.no wrote:
>>> Hi,
>>>
>>> I have two SAN-clients accessing the MD3000i.  The first client
>>> works just fine, but the second does not.
>>>
>>> I think I configured them similarly on the first and second server,
>>> so I'm thinking something is wrong.
>>>
>>>
>> You are not trying to access the same LUN from both are you ?. I'm not
>> sure the MD3000i supports shared file systems.
>
> The same LUN?  Well, it might be that some of the host-to-virtual-disk
> mappings
> had the same LUN - but I didn't know that mattered?  I see there are 4
> "Access"
> disks mapped to different hosts which all have the LUN 31.
>
> I've got 3 virtual disks setup now, each has its own host with an iSCSI
> initiatior.
>
> One interesting thing;  I got an IO Error message when using the first
> controller,
> but not on the second!
>
> -Morten
>
> --
> Morten W. Petersen
> Manager
> Nidelven IT Ltd
>
> Phone: +47 45 44 00 69
> Email: morten at nidelven-it.no
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at lists.us.dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>